# The case of the progress callback that never got called when progress happened

DevFeed: [The case of the progress callback that never got called when progress happened](<https://devfeed.tech/articles/the-case-of-the-progress-callback-that-never-got-called-when-progress-happened-21755.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/oldnewthing/20260903-00/?p=112672>)

Author: Raymond Chen

Published: 2026-09-03T14:00:00Z

Content type: article

Language: en

Sources: [Raymond Chen](<https://devfeed.tech/sources/raymond-chen.md>)

Topics: [debugging](<https://devfeed.tech/topics/debugging.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [debug](<https://devfeed.tech/topics/debug.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [breakpoint](<https://devfeed.tech/tags/breakpoint.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [code](<https://devfeed.tech/tags/code.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [handler](<https://devfeed.tech/tags/handler.md>), [old-new-thing](<https://devfeed.tech/tags/old-new-thing.md>), [providers](<https://devfeed.tech/tags/providers.md>)

## AI overview

A progress callback is never invoked because an intermediary method returns its own operation without forwarding progress reports from the provider's underlying operation. The suggested fix is to return the provider's operation directly so callers can attach to its progress.

## Source excerpt

Are you talking to the right guy? The post The case of the progress callback that never got called when progress happened appeared first on The Old New Thing.