The former is the base class for the latter, so this will widen the umbrella to catch a few corner cases that would otherwise been handled by the generic "Exception" catch block. One corner case I know of is when an op is canceled via "CancellationToken.ThrowIfCancellationRequested". In that case, an OperationCanceledException is thrown (not a TaskCanceledException). https://stackoverflow.com/questions/34359129/operationcanceledexception-vs-taskcanceledexception-when-task-is-canceled