Power Automate: Shutdown After 14 Days of Sustained Throttling (FAQ)

When a flow in Power Automate repeatedly hits throttling limits over an extended period, Microsoft eventually steps in: the flow is turned off automatically. This is not a coincidence or a platform glitch, but a documented safeguard meant to prevent a single flow from permanently blocking capacity without anyone intervening. For flow creators, it still often feels like a shock moment, especially when the flow is business-critical and suddenly shows as "Off" without a clear error message in the inbox. As of: July 2026.

This FAQ explains exactly when the automatic shutdown after sustained throttling kicks in, how you can tell whether your flow is affected, and how to reactivate it cleanly afterward without the problem immediately repeating.

What does "continuously throttled" actually mean?

Power Automate sets throughput limits for every flow and every connector, that is, how many actions or requests may be executed within a given time window. If a flow exceeds one of these limits, its execution is not stopped immediately but slowed down. According to the official documentation Limits for automated, scheduled, and instant flows flow activity automatically resumes once usage in the sliding time window drops back below the limit. It only becomes a problem when that doesn't happen and the flow stays constantly over the limits for an extended period. That's exactly when the 14-day rule kicks in.

Typical triggers for sustained throttling are too many actions per run, nested "Apply to each" loops, a trigger that fires too often, or a connector that responds to error code 429 ("Too Many Requests") because the underlying service limit has been reached. Such errors usually first show up as a noticeable delay in the flow run, long before the shutdown itself becomes visible.

The 14-day rule in detail

Microsoft describes the rule in Understand platform limits and avoid getting throttled like this: All flows that are continuously throttled for 14 days are turned off. These flows can be reactivated at any time, but if performance doesn't improve, the platform will turn them off again. So the shutdown isn't a one-time event but a recurring mechanism as long as the underlying cause remains.

Important for context: this 14-day throttling deadline is not the only retention limit in Power Automate. The limits table for duration and retention limits lists several similarly named but distinct rules side by side:

• Failing flows: A cloud flow whose trigger or action fails continuously is turned off after 14 days.
• Continuously throttled flows: A cloud flow that hits throughput limits constantly for 14 days is turned off. A Power Automate Process license can provide dedicated capacity and avoid throttling.
• Flows without trigger activity: A cloud flow that isn't triggered for 90 days can also be turned off, though only after a 30-day advance warning email to the owner and co-owners.

Because these three cases are easy to mix up in practice, it's worth checking the notification email from Power Automate: it usually states clearly whether the reason for the shutdown was errors, throttling, or inactivity.

How to prevent a shutdown

The most obvious immediate step is to edit the flow and save it again. Since throughput limits, according to Microsoft, apply to a single version of the flow definition, making a change and saving it again resets the time window. That buys you time, but it doesn't fix the actual root cause.

For a lasting solution, the following steps are worth considering:

• Reduce actions: Resolve nested loops, replace "Apply to each" with filtered queries using `$filter` or `$top`, and remove unnecessary intermediate steps.
• Ease off the trigger: Restrict a trigger that fires too often using trigger conditions, or adjust the polling frequency.
• Distribute the load: Split large volumes of data across multiple flow runs or child flows instead of processing everything in a single run.
• Check your license: A Power Automate Process or Premium license noticeably raises the allowed limits per flow and can make the decisive difference when capacity is tight.

In the Power Automate error code reference you'll also find specific guidance on individual timeout and throttling errors, in case you want to pinpoint the exact error source in the flow run history.

Reactivating a flow: what happens afterward

After the shutdown, a flow can be switched back on manually at any time. According to Turn a flow on or off a click on "Turn on" on the detail page, or "Turn on" via the context menu in the flow overview, is enough. What happens to events that piled up afterward depends on the trigger type:

• Polling triggers such as the Recurrence trigger check the connected service at fixed intervals. When the flow is turned back on, the trigger works through all events that accumulated since the shutdown, which can cause a noticeable backlog after a long period of inactivity.
• Webhook triggers register with the respective service and, after being turned back on, only process new events. Anything that happened during the shutdown is lost.

If you don't want this backlog, according to the documentation the only option is to duplicate the flow and delete the original, which cleanly re-registers the trigger. That way you retain control over which data actually gets processed, instead of being surprised by a flood of catch-up runs. Anyone who wants to run such automations reliably long-term shouldn't ignore throttling warnings in the first place, but factor them into capacity planning early, for example as part of ongoing automation projects.

Frequently asked questions

Is my flow shut down immediately as soon as it gets throttled once?

No. A single instance of throttling only slows the flow down temporarily, and it continues running automatically once usage drops back below the limit. The shutdown only happens once the flow stays continuously over the limits for 14 days.

How can I tell whether throttling was the reason for the shutdown?

Power Automate notifies flow owners and co-owners by email as soon as a flow is disabled. You can also check the analytics report on the flow's detail page to see how often the flow produced error code 429 or delayed executions over the past few days.

Does simply saving the flow reset the 14-day deadline?

Yes, with a caveat. Because throughput limits apply per version of the flow definition, the time window restarts after every save. That buys short-term relief, but it doesn't fix the actual cause of the throttling if the flow structurally triggers too many actions.

What happens to events that piled up during the shutdown?

It depends on the trigger type. Polling triggers such as the Recurrence trigger catch up on accumulated events once turned back on, while webhook triggers only process new events from the moment of reactivation onward and skip older events.

Does a Premium or Process license help against the automatic shutdown?

A Power Automate Process license provides the flow with dedicated capacity and higher limits, significantly reducing the risk of sustained throttling. According to Microsoft, it's the recommended measure for flows that structurally run close to the limits, but it doesn't replace optimizing inefficiently built flows.