Introduction

Cancelling an asynchronous workflow and waiting for that cancellation are not the same operation. Cancellation usually means sending a request that the workflow should stop. Waiting means observing when the workflow has actually acknowledged that request and finished unwinding. Good async design treats those as separate steps.

Cancellation Is Usually Cooperative

In most async systems, cancellation does not forcibly kill work at an arbitrary instruction. It signals intent, and the running task cooperates by checking that signal and exiting cleanly.

1using System;
2using System.Threading;
3using System.Threading.Tasks;
4
5static async Task RunAsync(CancellationToken token)
6{
7    while (true)
8    {
9        token.ThrowIfCancellationRequested();
10        await Task.Delay(100, token);
11    }
12}

This workflow can be canceled, but only because it observes the token and allows cancellation to flow through awaited operations.

Request Cancellation, Then Await the Task

The usual pattern is: call Cancel, then await the task that is being canceled.

1using var cts = new CancellationTokenSource();
2Task work = RunAsync(cts.Token);
3
4cts.Cancel();
5
6try
7{
8    await work;
9}
10catch (OperationCanceledException)
11{
12    Console.WriteLine("Workflow canceled cleanly.");
13}

The await is the part that waits for cancellation to complete. Calling Cancel alone only sends the request.

Why Waiting Matters

If you cancel and immediately dispose shared resources, close connections, or start replacement work without waiting, the original workflow may still be running briefly. That can cause race conditions, confusing logs, or corrupted shared state.

Waiting is therefore part of correct shutdown, not just a cosmetic detail. It tells you that the async workflow has actually reached a canceled or completed state.

Design Workflows to Reach Cancellation Points

A task that never checks its token, blocks in a non-cancelable call, or swallows cancellation exceptions may appear uncancelable even though a token exists.

That is why cancellation design starts inside the workflow. If the code does not have natural cancellation points, there is nothing meaningful to wait on except eventual completion.

Separate Cancellation from Failure

A canceled workflow should usually be distinguished from a faulted workflow. Those are different outcomes, and treating them the same makes diagnosis harder.

In many runtimes, a canceled task propagates a specific exception or task status. Use that signal deliberately instead of collapsing it into generic error handling.

That distinction helps shutdown logic too. A task that honored cancellation behaved correctly, while a task that failed during shutdown may need separate investigation.

Timeouts and Linked Tokens

Sometimes you want cancellation because a parent operation ended or because a timeout expired. In those cases, linked or timed cancellation sources help express why the workflow should stop.

The waiting pattern stays the same, though: signal cancellation, then await the task so cleanup and completion are observable.

The same principle applies when several tasks are running together. If one task is canceled, you still need to decide whether the others continue, cancel too, or get awaited as part of a coordinated stop.

Clear ownership rules make that choice much easier.

Common Pitfalls

• Assuming calling Cancel means the work has already stopped.
• Ignoring the canceled task instead of awaiting it to completion.
• Writing workflows that never observe the cancellation signal.
• Treating cancellation and failure as the same result.
• Disposing shared resources before the canceled workflow has actually exited.

Summary

• Cancellation requests and waiting for cancellation are two separate steps.
• In cooperative async systems, workflows must observe cancellation signals to stop cleanly.
• Call Cancel, then await the running task.
• Waiting matters because cleanup and shared-state safety depend on real completion.
• Design the workflow with regular cancellation points if you want cancellation to be responsive.