Hi @William_Crowell and @Fory_Horio,
The errors indicate that at some point the sharding metadata was stale/out of sync.
Usually invalidation the cache on the mongos/shards should solve this:
- However, where to run it depends on the version of the cluster.
Can you confirm the issue is gone now?
Best regards,
Pavel