tx-committed? checks whether a given transaction has committed and then returns true or false if so/if not. It can also throw NodeOutOfSyncException if the node hasn’t indexed that transaction yet. Assuming the node is in-sync, is there any reason that tx-committed? can return false other than an unsuccessful CAS? To put it another way, is the only possible error a NodeOutOfSyncException or could something fail for another reason (e.g., out of memory, out of disk space, etc.)? I would assume that if I submit a CAS, I would want to check tx-committed? and then retry the transaction if it returns false, which signals that somebody changed the document when I wasn’t looking. But if it returns false for other reasons, that might result in an infinite loop of retries. But then how would I distinguish those failures? Or is the plan that every other failure would be signaled by throwing an exception, and the only exception right now is NodeOutOfSyncException? And yes, I have one of those minds which naturally picks out corner cases far away from the happy path. 🙂