Right now a concurrent drop might run concurrently with a rename, causing the command to fail with NamespaceNotFound. This behaviour is fine and expected, however, we could check if the NamespaceNotFound came from the first check done on the command specifically, by checking for the changelog collection.