Applies to Product - Microsoft Dataverse
What’s happening?
Customers may encounter an exception stating that the transaction of the SQL command has already been rolled back or committed. This issue is often associated with a swallowed SQL deadlock exception.
Reason:
The underlying cause of this is typically related to SQL deadlocks, which occur when multiple processes acquire resources in a cyclical manner, leading to a situation where SQL cannot proceed until one of the processes is terminated.
Resolution:
- If this occurs, advise users to retry the operation, as transient deadlock errors are common in highly concurrent transactional systems and the operation is likely to succeed upon retry.
- If the deadlock errors are frequent or consistently occurring for specific operations, further investigation may be required to address the underlying cause.
- Reducing concurrency can help minimize the likelihood of encountering deadlock errors.