Business Event Latency and Delays triggering multiple Power Automate Flows after 10.0.47 Update

Nickdalag 0 Reputation points
2026-05-19T12:23:37.6233333+00:00

Hi everyone,

We recently updated our sandbox and production environments to Dynamics 365 Finance and Operations Version 10.0.47. Since the update, we are experiencing severe processing delays/latency with Business Events that trigger multiple Power Automate flows simultaneously.

This issue primarily presents itself during peak rush hours when transactional volume is high. Prior to 10.0.47, this exact setup handled the load smoothly.

Our Questions:

Has anyone else experienced a regression in the background batch or Business Events framework capacity with the rollout of 10.0.47?

Are there any newly introduced features or telemetry overheads in 10.0.47 that affect the concurrency or thread management of the BusinessEventsProcessor job?

Is this a known platform performance issue?

Any insights or recommendations would be greatly appreciated!

Azure Logic Apps
Azure Logic Apps

An Azure service that automates the access and use of data across clouds without writing code.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-19T12:23:54.1733333+00:00

    There is no information in the provided context that indicates a known regression, capacity reduction, or new telemetry overhead in Dynamics 365 Finance and Operations 10.0.47 that specifically affects the Business Events framework or the BusinessEventsProcessor batch job, nor anything that ties 10.0.47 to degraded performance of Power Automate flows triggered by business events.

    The only relevant business‑event guidance in the context is generic troubleshooting, not version‑specific:

    • If business events are not triggering or are limited by configuration, verify the parameters in the BusinessEventsParameters table (in System administration > Setup). For non‑production environments, the documented baseline values are:
      • Retry count = 3
      • End points allowed per event = 10
      • Wait time = 1000 After changing these, restart the batch service and run IISReset so the new values are picked up.
    • If there are errors on active business events such as Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information, rebuild the business events catalog.

    For Dataverse‑based Power Automate triggers, the documented causes of multiple or delayed triggers are also generic and not tied to 10.0.47:

    • Multiple triggers for the same change can be caused by duplicate callback registration records for a flow. Removing duplicate callback registrations (via Dataverse API or by turning the flow off and on) resolves this.
    • Multiple updates to the same record in quick succession will legitimately fire multiple triggers; audit history can be used to identify the source and then add de‑duplication logic in the flow.
    • Delays can be caused by normal asynchronous processing in Dataverse, or by backlog in the async service. If delays exceed about five minutes, System Jobs should be checked for backlogs; persistent issues should be escalated to Microsoft support.

    The platform and Finance 10.0.47 “what’s new” content in the context lists feature additions and schedule details but does not mention any change to Business Events capacity, concurrency, or threading, nor any known performance issue in this area.

    Given the context, there is no documented 10.0.47‑specific regression or known issue for Business Events or Power Automate triggering. Only the generic configuration and troubleshooting steps above are available.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.