Cloud flow keeps on running and not completing

[deliah]

Hello, 

I have a cloud flow that has been running successfully, it is working perfectly for days.

Currently the run history for flow, the flow was stuck for more than 12 hours after it becomes kept running and not completing. 

Almost as it is stuck on a "Apply to each" step, and it keeps running with no end.

My flow purpose is to record the file version of the SharePoint folder regularly.

It usually takes less than 10 mins for each run.

The flow was stuck for more than 12 hours, and it keeps running with no end.

Please advise, thanks.

[Johnnyg · Accepted solution]

Hello deliah,

There are number of possible causes to slow running flows:

• The service you are connecting to is running slowly.

  • For instance, a slow running SQL query will cause a flow to slow down while it waits for query execution to complete.

• The connector you are using is slowing your flow down as a service protection mechanism.

  • For example, the SharePoint connector caps actions at 600 per minute. A single SharePoint connection used across multiple flows can still only execute 600 operations per minute.

    • Most connector pages have a Throttling Sectionthat documents this limit.

  • You might see a 429 (Too Many Requests) error in your flow with error text like like "Rate limit is exceeded. Try again in 27 seconds."

• Your flow is executing an excessive number of actions per day, far in excess of the daily action limits for your plan

  • You can see the minimum number of actions that the Power Automate service will allow for each plan on the Request limits and allocation page.

  • Every card in a flow that gets executed counts as an API call (action). This includes both actions that result in outgoing calls (e.g. calling SharePoint) and actions that don't (e.g. variable setting, delays, etc.). Only completed and failed actions (but not skipped) count toward the limit.

  • The Power Automate service typically allows higher counts than are documented here, and will not slow flows down based on occasional and reasonable overages. However, if your flows have action counts above these limits, they are subject to potential throttling, or in cases of extended violation, disablement.

  • You can utilize the analytics tab of the flow details page to diagnose actions usage.

• Your flow is exceeding the data consumption allowance per day.  This is the amount of data your flow consumes as a result of the input/output operations.

• Your flow is exceeding a limit that is documented on the Power Automate limits and configuration page.

  • For these particular throttles, both executed and skipped actions (as might happen in an if/else branch) count toward the limit.

  • Violating plan limits documented in the below table is much more common.

Please check below official slow run Flow suggestion for more details.

https://support.microsoft.com/en-us/topic/troubleshooting-slow-running-flows-2a51dcd6-0b21-33da-5ce8...