CollectionRouter/MultiCollectionRouter performs retries for any StaleConfig exception, regardless of whether the stale namespace is one involved in that particular router loop. This leads to unnecessary retries when the stale version is one provided by the issuer of a command, but then the execution on the targeted shard reaches a CollectionRouter to perform additional routing (e.g. when executing a lookup, additional routing is performed for the inner collection).