Applies to Product - Microsoft Dataverse
What’s happening?
The organization service is intermittently throwing errors indicating that the initialization of the database connection or transaction has failed. The error message suggests that this operation should be retried later.
Reason:
This is related to the databases hosted on Azure Cloud infrastructure's Elastic pools. These pools undergo continuous proactive and reactive maintenance activities by Azure, which dynamically balance the database load across pools. During these load-balancing transitions, brief connection failures may occur, resulting in errors such as 40613.
Resolution:
- Ensure that any customer workload or application connecting to the database implements a robust retry mechanism to handle transient connection failures effectively.
- Monitor the system for timeout errors. If timeout errors persist for more than 10 minutes, further investigation may be required.
- Review backend telemetry to identify any performance slowdowns or patterns related to the errors encountered.
- If issues continue, engage with the product team for deeper analysis and potential fixes.