It's possible that maybe the routing table gets flushed or becomes stale through move chunks or a drop collection, which could cause the chunk manager on the clusterQueryWithoutShardKey to return NamespaceNotFound.

In the case where a collection is dropped before the command is run, uasserting InvalidOptions when checking if the collection is sharded may prevent retrying on StaleConfig exceptions. It may be necessary to adjust the error handling here.