Views:

Applies to Product - Microsoft Dataverse
 

What’s happening?
Customers are experiencing significant delays in data row change events for Power Automate and Logic Apps, with workflows triggering after 20 to 30 minutes. Additionally, there are errors encountered when attempting to import opportunity records, indicating that a database resource is currently in use by another request.
 

Reason:
The delays in triggering workflows may be caused by several factors, including: - Asynchronous backlog in operations. - High concurrency settings leading to system overload. - Incorrect or overly broad trigger conditions. - Callback registration issues preventing timely triggering.
The resource lock error indicates that there may be a high number of requests attempting to use the same database resource simultaneously.
 

Resolution:

  1. For Delays in Data Change Events:
  2. Verify the flow configuration to ensure the trigger is set correctly.
  3. Check the organization's status to confirm it is not in admin-only mode or suspended.
  4. Investigate any asynchronous backlog that may be causing delays.
  5. Ensure that callback registration records exist and match the current flow definition.
  6. Implement wait conditions in the flows to manage timing effectively.
  7. For Resource Lock Errors:
  8. Review the number of concurrent requests being made to the database.
  9. Consider reducing the number of simultaneous operations to avoid resource contention.
  10. If the issue persists, consult with the relevant team to analyze the database performance and request handling.
If the above steps do not resolve the issues, further investigation may be required, and additional details should be collected for a more in-depth analysis.