How to use CancellationTokens to cancel tasks in the Azure SDK for .NET



The ability to cancel long-running tasks is important to help keep applications responsive. Whether the network connection is slow or disconnects, or the user just wants to cancel a long task, using a CancellationToken in .NET makes it easy to cancel those long tasks. Together with a CancellationTokenSource, a developer can provide on-demand or timed cancellations of tasks that accept a CancellationToken, like our client methods in the Azure SDK for .NET.

Using CancellationTokens

Prior to the introduction of the CancellationToken structure in .NET Framework 4.0, it was common to use one or more WaitHandle objects to synchronize threads. This same pattern has been used in native Windows applications for decades. When the asynchronous task pattern was introduced in .NET, a new, simpler pattern for cancelling tasks was also introduced. While a CancellationToken can still provide a WaitHandle to synchronize threads, creating tokens and passing them to methods is much easier:

CancellationTokenSource cts = new CancellationTokenSource();
KeyVaultSecret secret = await secretClient.GetSecretAsync("my-secret", cts.Token);

CancellationTokenSource.Token returns a CancellationToken that can be passed to other methods further down the call stack, or even on other threads. When those tokens are canceled, any methods waiting on them should throw an OperationCanceledException. Methods accepting a CancellationToken don’t even have to be asynchronous. Our synchronous client methods in the Azure SDK for .NET also accept a CancellationToken. In both synchronous or asynchronous code, you can simply call CancellationToken.ThrowIfCancellationRequested() to immediately throw if the token was in a canceled state.

public void DoWork(CancellationToken cancellationToken = default)

    // Start long-running task...

Notice that we didn’t have to check if cancellationToken was null. As a value type in .NET, it cannot be null and even defined as its default value, CancellationToken.ThrowIfCancellationRequested() will simply do nothing.

If you don’t want to throw an exception but still want to check if a token was cancelled, you can check the CancellationToken.IsCancellationRequested property.

Cancelling CancellationTokens

You’ve seen a few ways to pass and use a CancellationToken, but how do you actually cancel them? That ability is supported by the CancellationTokenSource. A CancellationTokenSource can cancel tokens on demand or after a certain amount of time:

CancellationTokenSource cts = new CancellationTokenSource(TimeSpan.FromSeconds(30));
Console.CancelKeyPress += (source, args) =>
    Console.Error.WriteLine("Cancelling download...");

    args.Cancel = true;

Console.WriteLine("Downloading to {0}...", path);

    using (Stream fs = File.Create(path))
    await blobClient.DownloadToAsync(fs, cts.Token);
catch (OperationCanceledException)
    Console.Error.WriteLine("Download canceled. Deleting {0}...", path);

We created a CancellationTokenSource that will cancel all its tokens after 30 seconds, and also hooked up a handler for pressing Ctrl+C in this sample console application. This way, we provide flexibility to the user to cancel the task whenever they want, and also cancel the task if it takes too long, which might indicate a network error if a suitable timeout is chosen. If the download is cancelled, we can handle the OperationCanceledException to delete the file in case it was partially downloaded.

Cancelling Long-running Operations in Azure SDK

A subtle but important distinction is that long-running operations (LROs) in Azure SDK often refer to specific classes like CertificateOperation. After methods that return LROs like StartCreateCertificateAsync have completed, canceling a CancellationToken passed to any methods like CertificateOption.UpdateStatusAsync only cancels waiting on that method. To cancel an LRO, you need to call Cancel or CancelAsync on the LRO to actually cancel the operation.

CertificateOperation op = await certificateClient.StartCreateCertificateAsync("my-certificate", certificatePolicy);

// After some time, user decides to cancel certificate creation.
await op.CancelAsync();

These long-running operations (LROs) can often take longer than most programs are expected to run. Creating a certificate, for example, could take days of approvals. These LROs can be recreated – like in this example, using the pending certificate name – and code can continue to wait or cancel them later.

Advanced uses

Despite its simple design, a CancellationToken can be used in a number of other scenarios.

Doing additional work when canceled

Canceling any current or pending work is a typical scenario when a CancellationToken is canceled. In some scenarios, you might need to do some clean up only when canceled. For this reason, you can register a delegate to run only when the CancellationToken is canceled. Registering a delegate returns an IDisposable which can be disposed to unregister the delegate if no longer needed. We could log a message, for example, that a method was canceled without worrying where in code to write the message:

public async Task DoWorkAsync(CancellationToken cancellationToken = default)
    using (CancellationTokenRegistration  cts = cancellationToken.Register(() =>
        Console.Error.WriteLine("The task was cancelled.");
        // Start long-running task...

Linking CancellationTokens

There may be times when you have a group of tasks you want to cancel individually or all together, for example downloading as many files as possible and reporting on those that failed. You can link a CancellationToken to a new CancellationTokenSource so that when that original CancellationToken is canceled, any tokens created from a linked CancellationTokenSource are canceled:

public async Task DownloadAsync(Uri uri, CancellationToken cancellationToken = default)
    using (CancellationTokenSource cts = CancellationTokenSource.CreateLinkedTokenSource(cancellationToken))

        // Download file ...

It’s important to note that linked CancellationTokens only work in one direction: canceling a CancellationToken from a linked CancellationTokenSource does not cancel the original CancellationToken.

Waiting on handles

You can also use a CancellationToken with code that requires waiting on one or more WaitHandle objects. This may be common for older applications or when interoperating with native code like with P/Invoke. The CancellationToken.WaitHandle can be used in calls like WaitHandle.WaitAny:

AutoResetEvent evt = new AutoResetEvent(false);
ThreadPool.QueueUserWorkItem(state => DoWork(state, evt));

int which = WaitHandle.WaitAny(new WaitHandle[] { evt, cancellationToken.WaitHandle});
if (which == 1)
    Console.Error.WriteLine("The task was canceled.");

Updating APIs for older applications to use newer classes like CancellationToken may help when upgrading to newer components.

Further reading

Want to hear more?

Follow us on Twitter at @AzureSDK. We’ll be covering more best practices in cloud-native development as well as providing updates on our progress in developing the next generation of Azure SDKs.

Contributors to this article: Heath Stewart.


Comments are closed.