When executing a write operation in a transaction it will always behave as an ordered:true write, it will stop on the first error it encounters. BulkWrite did not properly handle this on mongos where we made assumptions based only on the value of ordered and not also based on if we are in a transaction. This could cause us to hit a tripwire assert if the bulkWrite caused a non-transient error to occur during execution.