When transactions are used, I believe reads are done with snapshot read concern. As such if QC is enabled, it might be necessary to create a subscope for the duration of the transaction where reads would be performed again, and when a transaction is retried reads should also be perhaps performed again. Or perhaps simply flushing cache when transaction starts and when commit is started would be sufficient.

We might need a way to reliably trigger transient errors for testing purposes.