During a transaction, if a CommitTransaction times out, the client session state is still moved to "Committed".

This is inaccurate, as the operations within the commit will not have actually reached the server, so the transaction is not "Committed". Furthermore, if users attempt to abort the transaction when the CommitTransaction fails, they will encounter a "cannot call abortTransaction after calling commitTransaction" error, which is likely an unexpected error.

The issue is likely here, where we set session state to "Committed" without checking for potential errors from operation execution.