Power Automate Flow Not Starting: The 7 Most Common Causes

A Power Automate flow that suddenly stops starting almost always has one of seven causes in practice: incorrect or overly restrictive trigger conditions, an expired connector connection, automatic deactivation after 90 days without being triggered, a missing or expired license, a blocking DLP policy, an activated administration mode in the Power Platform environment, or an automatic shutdown due to permanently failing actions. Anyone who checks these seven points in order usually finds the cause within a few minutes, without having to rebuild the flow. As of: July 2026.

Which 7 causes most often stop a Power Automate flow?

According to Microsoft's official Power Automate documentation, the following seven reasons cover the vast majority of all flows that fail to start.

• Trigger conditions (Trigger Conditions) incorrect: If the trigger contains a condition that begins with the @ symbol, the flow only starts if this condition is met. If the condition is formulated incorrectly or refers to a field that does not exist in the event at all, the check is skipped and the flow does not start. Microsoft internally refers to this error as TriggerConditionNotMet.
• Expired connector connection: Connections to services such as SharePoint, Outlook or Dataverse expire if they are not used for a long time or if the password of the connecting account has changed. The flow remains switched on, but the trigger can no longer register with the service.
• Automatic deactivation after 90 days of inactivity: A cloud flow that has not been triggered for 90 days is automatically switched off by Power Automate, unless the owner has a premium or capacity license.
• Missing or expired license: A suitable Power Automate license is required for editing, manually triggering, or using premium connectors. If a trial license expires or is withdrawn, the flow remains visible but no longer starts.
• DLP policy blocks the flow: Data loss prevention policies determine which connectors may be used together in a flow. If a flow violates such a policy, it is paused and the trigger no longer fires.
• Environment problem due to activated administration mode: If administration mode is activated for a Power Platform environment, all background processes, including all flows in that environment, are deactivated.
• Automatic shutdown due to permanently failing actions: If a trigger or an action fails continuously for 14 days, Power Automate switches off the flow on its own to avoid further faulty runs.

Why exactly does Power Automate switch off flows after 90 days?

Microsoft explicitly limits the time without trigger activity to 90 days in the official limits for flows. Literally, it states there: a cloud flow that is not triggered within a period of 90 days may be deactivated, as documented by the Limits for automated, scheduled, and instant flows page. Flows from users with premium or assigned capacity licenses are exempt from this rule, and owners as well as co-owners are notified 30 days before the deactivation.

Anyone who misses this notification, for example because an internal mailbox is rarely checked or because the original creator has already left the company, simply finds the flow switched off the next time they look. Separately, a 90-day limit often also applies to individual connector connections, but at the level of the connection rather than the entire flow, as described by the Troubleshooting broken connections page using the example of the SharePoint connector. Both deadlines can overlap in practice and should be checked separately.

How do you find the specific cause in your own flow?

A fixed sequence of four checks leads to the goal fastest.

• Check execution history: Open the affected flow in "My flows" and check the 28 day execution history under "All runs" to see whether a trigger check was skipped. This indicates an unmet trigger condition.
• Check connection status: Under "Data" and "Connections", Power Automate shows which connection needs to be repaired, as also described by the Troubleshoot common trigger issues page.
• Review license and flow status: The flow's detail area shows the current license plan as well as whether the flow is marked as paused or suspended.
• Use the flow checker: When saving the flow, the built in flow checker reports DLP violations and missing permissions directly in the editor.

If larger Power Automate landscapes with multiple environments and license models are in use, a structured Power Automate consulting engagement that goes through trigger logic, license distribution, and DLP policies completely in one pass is often worthwhile, instead of debugging each flow individually.

Frequently asked questions about Power Automate flows that do not start

Why was my flow deactivated without warning?

According to Microsoft, this does not actually happen completely without warning. For the 90 day inactivity rule, notifications are sent to owners and co-owners 30 days in advance; for continuously failing runs, deactivation takes effect after 14 days. The most common reason the deactivation still seems surprising: the notification email lands in a rarely checked mailbox, or the original creator has already left the company.

Is it enough to simply switch the flow back on?

In the case of deactivation due to inactivity or repeated errors, switching it back on is often enough, provided the underlying cause has been fixed. In the case of an expired connection or a missing license, you must also reauthorize the connection or assign the license, otherwise the next run will fail again immediately.

How do I distinguish a trigger condition from a DLP block?

An unmet trigger condition shows a skipped trigger check in the execution history, while a DLP block triggers an explicit error message from the flow checker when saving the flow, pointing to the violated policy. When in doubt, it helps to look at both places, because from the outside both error patterns initially look the same, namely a flow that simply does not run.

Does the 90 day rule also affect frequently used flows?

No, the rule only applies if a flow has not been triggered a single time within 90 days. Regularly running flows, such as daily or weekly recurrence triggers, are not affected by this, regardless of the license type.