Several index build JS tests that set up prepare transactions (startTransaction + insert + prepareTransaction) fail intermittently when run in the noPassthrough_primary_driven_index_builds suite under burn-in conditions. The suite injects WTWriteConflictException at 0.1% probability, which can fire on transaction inserts and produce TransientTransactionError. The affected tests do not retry on this error and fail. A targeted fix has been applied to index_abort_stepdown_prepare.js and index_stepdown_prepare_conflict.js; index_stepdown_commit_prepare_conflict.js has the same gap and may surface similarly. A more transparent solution would be a suite-level override that automatically retries TransientTransactionError for any test in the suite, which would also allow removal of the per-test retry logic already added.