Recent update slows Power Automate flows triggered by business events
Users report that Business Events now launch multiple Power Automate flows at the same time. Each flow takes noticeably longer to begin processing after the event occurs. The change followed an unspecified update to the Business Events service. No official workaround or fix has been published. Flows that previously started within seconds now show increased execution times when several instances run from one event.
Before the update, a SharePoint list change or Teams message could be trusted to start an approval flow almost immediately. Teams built their daily processes around that assumption. Now the same event can leave the first flow waiting while a second instance starts later, so approvals sit in queues and notifications arrive after the decision window has passed.
Analysis
Stop treating Business Events as reliable real-time triggers. Add a condition at the top of every affected flow that checks the age of the incoming data and aborts if it is older than your SLA.
Pulse published by Collab365 Spaces. Cite as "Recent update slows Power Automate flows triggered by business events", Collab365 Spaces. 1 source referenced.