However, if your flows have action counts above these limits, they are subject to potential throttling, or in cases of extended violation, disablement. The Power Automate service typically allows higher counts than are documented here, and will not slow flows down based on occasional and reasonable overages. Only completed and failed actions (but not skipped) count toward the limit. calling SharePoint) and actions that don't (e.g. This includes both actions that result in outgoing calls (e.g. 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.Įvery card in a flow that gets executed counts as an API call (action). Your flow is executing an excessive number of actions per day, far in excess of the daily action limits for your plan You might see a 429 (Too Many Requests) error in your flow with error text like like 'Rate limit is exceeded. Most connector pages have a Throttling Sectionthat documents this limit. A single SharePoint connection used across multiple flows can still only execute 600 operations per minute. The connector you are using is slowing your flow down as a service protection mechanism.įor example, the SharePoint connector caps actions at 600 per minute. The service you are connecting to is running slowly.įor instance, a slow running SQL query will cause a flow to slow down while it waits for query execution to complete. There are number of possible causes to slow running flows: This article does not apply to triggers not firing. Note that this is distinct from triggers not firing, in which case the flow will not even start or show up in the run history list.

Flow actions seem to be running slowly, and may appear to get stuck on a single step in the flow run viewer.

School mate 2 running very slowly