cancellation-tokens-ai-kit

To propagate CancellationToken through .NET async workflows, pass the same token down from controllers to services, repositories, and EF Core async calls. This ensures long-running operations stop promptly without leaving your app in an inconsistent state.

HttpContext.RequestAborted provides the upstream CancellationToken for web endpoints. You wire this token into your controller and pass it directly to your EF Core async calls to safely cancel database queries when the client disconnects.

The best way to handle OperationCanceledException in .NET background services is to catch it during graceful stopping. Use explicit IsCancellationRequested checks inside long-running loops to ensure background operations terminate safely.

Yes, you can use CancellationTokenSource for timeouts in HttpClient calls. The skill applies correct token propagation and explicit cancellation checks to safely handle timed-out HTTP requests and downstream async operations.

Your long-running async loop does not stop because the CancellationToken is not checked or propagated. You must call ThrowIfCancellationRequested inside the loop and pass the token to async methods like Task.Delay to ensure prompt termination.

Yes, you need to check IsCancellationRequested or call ThrowIfCancellationRequested in addition to passing the token. Explicit checks are required inside long-running loops to guarantee immediate cancellation between asynchronous operations.