For versions before 5.3, after a migration the recipient shard most of the time will not know that it has received a chunk, until a more recent router comes to look for it. Currently set_fcv_prepared_transaction.js does not account for these StaleConfig errors and mongos implicitly aborting the transaction.