Help for owners
My Power Automate flows keep failing or hit their limits
Short answer
Power Automate fails for a few documented reasons: a connection that needs signing in again, a licence that does not cover a connector, a daily action limit, a run longer than 30 days, or a flow switched off after repeated errors. Read the error on the first failed run before you change the flow.
Does this sound like your situation?
- The flow shows failed runs, or is marked Off or Suspended.
- It worked for months and stopped after a person left or changed their password.
- The error mentions a licence, a premium connector or too many requests.
- A long approval or wait never finishes.
- The flow has become a long chain nobody dares to touch.
Why does this happen?
The connection behind the flow expired
Microsoft lists password changes, a changed sign-in policy, revoked consent and about 90 days of inactivity as reasons a connection breaks. The fix is to sign the connection in again; for key flows Microsoft suggests service principal connections, which do not depend on one person's login.
Confirmed by learn.microsoft.com
The licence does not cover what the flow uses
Microsoft's error reference says premium connectors such as HTTP need a premium licence for the person who runs the flow, and that a scheduled flow can fail when its owner loses that licence.
Confirmed by learn.microsoft.com
The flow hit a platform limit
Microsoft documents a 30-day maximum run duration, so a pending approval times out after that. It also documents request limits per 24 hours by performance profile, and says a flow that stays over its limits for 14 days is turned off.
Confirmed by learn.microsoft.com
Repeated failures switch the flow off
Per the same page, a flow with continuously failing steps is turned off after 14 days, and a flow not triggered for 90 days might be turned off. If the owner leaves the company, the flow reverts to the Low performance profile.
Confirmed by learn.microsoft.com
A policy changed and blocked a connector
Microsoft says data loss prevention policy changes take effect immediately, and that when several flows break at once a policy change is the most likely cause.
Confirmed by learn.microsoft.com
What can I do about it today?
- Look at the flow's statusOn, Off or Suspended tells you whether it is a stop or a failure. Do not turn flows on and off repeatedly while you investigate.
- Open the first failed runNote the red step, the error code and the time. Microsoft's reference explains each code, such as 401, 403, 404 and 429.
- Check who owns the flow and the connectionsIf the owner has left, ask your Microsoft 365 admin to move ownership. Do not share your own password to make it work.
- Ask your admin whether a policy or licence changedSeveral flows breaking on the same day points to a policy change rather than to the flows.
- List the flows the business depends onName each one, who owns it and what it touches. You cannot judge limits until you know what is running.
When should I bring someone in?
- Limits or licence errors keep returning and the flow is business critical.
- One flow has grown into dozens of steps and nobody can explain it.
- You need the same logic to run reliably outside Power Automate, in code you own.
How do I handle it?
- Inventory firstI list the flows, their owners, connections and what each one reads or writes, before changing any of them.
- Separate failures from limitsRun errors, licence errors and platform limits need different fixes, so I sort the failures by cause using Microsoft's own error reference.
- Repair, then protectI fix the failing step on a copy, then add failure alerts and move key flows to connections that do not hang on one person.
- Judge whether it still fits the toolIf a flow needs heavy loops, big volumes or logic that is hard to test, I describe what a small code-based service would do instead, and you decide.
- Move only what is worth movingSimple flows stay where they are. Only the fragile or heavy ones are rebuilt in code you own, with logs and tests.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it a bug or a licence limit?
The error code tells you. Microsoft's reference separates connection errors, licence errors such as a missing premium licence, and throttling errors.
How long can a flow wait for an approval?
Microsoft documents a maximum run duration of 30 days. After that, pending steps time out.
Should I leave Power Automate?
Not by default. Small, simple flows are what it is for. Moving makes sense when a flow is business critical, heavy or hard to understand.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.