SERVER-76293 introduced a new consistency check called checkCollectionOptionsConsistencyAcrossShards, which launches an aggregation from the primary shard of the collection being processed across the cluster.

Such an aggregation requires a consistent and up-to-date routing table to be successfully performed, but it might face a situation where:

• the routing table is in a corrupted state (due to an overlap between contiguous ranges)
• the routing information cached on the primary shard is stale (so that such inconsistency goes undetected by the dedicated check that runs just before checkCollectionOptionsConsistencyAcrossShards).

When this happens, the corrupted routing table causes checkCollectionOptionsConsistencyAcrossShards to consistently return a ConflictingOperationInProgress error (caused by the impossibility of installing the refreshed routing information on the primary shard cache).