Back in SERVER-52693, we created the CursorInvalidatedError category and included OperationFailed among the errors in this category.

The set of errors was taken from this concurrency workload.

This is incorrect: OperationFailed signals to the caller that a definitive, non-transient error occurred and the operation failed. Simply retrying the operation will not resolve the underlying problem.

Today, Shard::RetryPolicy::kIdempotentOrCursorInvalidated retries CursorInvalidatedError errors for internally executed commands. In addition, ShardingCoordinator::_isRetriableErrorForDDLCoordinator() considers CursorInvalidatedError retriable.

The risk is that a command or function that failed with a non-transient error will be retried indefinitely. For coordinators, this could mean retrying while inside the critical section and stalling CRUD operations.

Remove OperationFailed from the CursorInvalidatedError category.