CancellationToken has taken what might have been a messy, hard to manage part of our application and made it pretty simple and lightweight.

Atomic Object is a software consultancy specializing in custom software development and product design. Readers can learn about software development methodologies, user-centered design principles, and agile practices. With case studies, blog posts, and technical insights, Atomic Object provides  guidance and expertise for building innovative and user-friendly software products.

Atomic Spin

CancellationToken in C# simplifies managing long-running jobs but has important limitations. Key lessons: tokens cannot be persisted outside memory, different libraries implement cancellation differently (Parallel.ForEachAsync immediately kills running tasks), and tokens don't automatically handle server restarts or deployments. While CancellationToken provides a solid foundation for graceful job cancellation, applications must be built to handle its boundaries and quirks, particularly around persistence, library-specific behaviors, and infrastructure-level shutdowns.

CancellationToken in C# – Pitfalls and Winning Patterns

Don’t Try to Persist the Token Out of Memory

Different Cancellation Implementation Across Libraries

The Limit of CancellationToken’s Authority

<p>so what is te solution if we wanna gracefully cancel?</p>


<p>I’ve experienced the “joys” of CancellationTokens directly while working with the Hangfire framework.  Somewhere between road rash from wiping out on a bicycle and a root canal with zero novocaine.</p>
