It uses the failCommand to make the command it is about to send next fail x number of times a certain way, but if a background thread happens to run a similar command to that shard, then the background thread will end up "consuming" the error instead of the test thread.

Looks like transactions_snapshot_errors_first_statement.js also have the same issue.