Dynamics 365 update adds delays to Power Automate flows triggered by business events
Microsoft released version 10.0.47 of Dynamics 365 Finance and Operations. Users report noticeable delays when Business Events attempt to start several Power Automate flows at the same time. The latency appears in both sandbox and production environments. No fix date has been announced. Business Events are the built-in signals Dynamics 365 sends when records change. Power Automate can listen to those signals to start flows automatically.
Before the update, a flow triggered by a Business Event would start within seconds of the record change. Teams treated this near-real-time behaviour as reliable enough to build approval chains and status notifications on top of it. After 10.0.47 the same flows now queue behind each other. A single record change can leave several flows waiting, and the user has no visibility into the queue or any way to prioritise one flow over another. The automation layer that once felt instantaneous now behaves like a shared resource with unknown contention rules.
Analysis
Treat Business Events as an unreliable dependency rather than a stable trigger. Move any flow that must run quickly or in sequence to a SharePoint list trigger or a scheduled check you control, then add a simple condition that skips duplicate runs.
Citation
This executive briefing was curated and analyzed by Collab365. To reference this analysis, please attribute: "This briefing is available on Collab365 Spaces (spaces.collab365.com)".