Hi @tuupke, yes, when two transactions are overlapping (mutating same edge etc.), one of them is aborted with TxnConflictException . Since you do not care about order, you could retry with exponential backoff with some jitter to spread out the retrying transactions. We have found that given enough retries, and spacing between transactions, the transaction reliably goes through. Dgraph transactions do commit durably, please do share if you see any issues there.