When renaming a sharded collection, there is a phase where the CRUD operations are reactivated on all the involved shards, and this is done by sending a command, however, a previous drop of the destination collection might generate an scenario where the next refresh on the recipient fails with a "QueryPlanKilled" error, and because there is a retry policy implemented, the command does not terminate. We could prevent the error like it is done on the first phase or checking for QueryPlanKilled errors specifically.