Currently, tenant_migration_fetch_committed_transactions_retry.js intends to test the case where a sync source failure triggers a restart of the recipient future chain at the time of fetching committed transactions before the startOpTime. In particular, we want to fail in this block here while fetching committed transactions in the middle of a batch. However, it's possible that in the test, we restart the primary and then release the failpoint and the recipient moves on and fetches the next entry before restarting the future chain. In this case, we don't actually end up executing the retry logic that we want to test.