Suspended Flows

Suspended flows can't hide here

A suspended flow doesn't run, doesn't fail, and doesn't say anything — it just stops. FlowOversee gives suspensions their own page, with the recorded reason next to each flow, so the quietest failure mode becomes the easiest one to spot.

Try it in the interactive demo See how it works →

Power Automate does the automating — FlowOversee adds the overseeing. It's a read-only companion to a platform we think is great: nothing in your flows changes, you just see them better.

Spotting suspensions by hand

  • Suspension is easy to miss — a suspended flow simply stops producing runs, and nothing chases you down about it.
  • In a quick scan of a flow list, a suspension can read as merely "stopped" until you open the flow itself.
  • The "why" lives inside each individual flow, one click-through at a time.

With FlowOversee

  • A dedicated page listing every flow currently suspended in the environment.
  • The state is checked at the detail level — where suspensions actually show — so one can't masquerade as merely stopped.
  • The suspension reason and details sit right in the list — search by flow or by reason.

The reason, up front

Each suspended flow is listed with the reason and detail text recorded for it — so triage starts with the why, not with a scavenger hunt. From the row, open the flow's details or jump to the maker portal to put it right.

  • Suspension reason and details shown per flow, right in the list
  • Search matches flow names and reason text
  • Live on every load — a fixed flow leaves the list the next time you look
FO Web Check
Suspended · left its active state
Suspended
FO Bulk Notify
Suspended · policy check
Suspended
FO Archive Sweep
Suspended · platform limits
Suspended

Hear about it when it happens

The page answers "what's suspended right now?" — background alerts answer "did anything just get suspended?" Turn on the suspension trigger and FlowOversee sends a Windows notification the moment a check finds a flow has left its active state.

  • A dedicated alert trigger just for suspensions — with its own on/off switch
  • Checks run every 2 minutes up to hourly, on the environments you choose
  • Every alert also lands on the in-app Alerts page with a sidebar badge
FlowOversee notification icon FlowOversee now
Flow suspendedFO Web Check — left its active state
FlowOversee notification icon FlowOversee 1h
Flow suspendedFO Bulk Notify — Production
Common questions

Suspended flows, answered

How do I find suspended flows in Power Automate?
FlowOversee gives suspended flows their own page: every flow in the environment currently in a suspended state, listed with the suspension reason and details Microsoft recorded. You can search by flow name or by the reason text.
Why did my Power Automate flow get suspended?
The platform can suspend a flow for several reasons — for example when it trips platform limits or a policy check. Whatever the cause, FlowOversee surfaces the suspension reason and detail text recorded for the flow, so you start with the why instead of hunting for it.
Can I get alerted when a flow becomes suspended?
Yes. FlowOversee's optional background alerts include a dedicated suspension trigger: the moment a check finds a flow has left its active state, you get a Windows notification and an entry on the Alerts page.
Works together

Pairs well with

Alerts

A Windows notification the moment a flow is suspended or turned off — its own trigger switch.

Explore Alerts →

Failed Runs

The loud failure mode: every flow whose last run failed, with the error inline.

Explore Failed Runs →

Daily Monitor

A suspended flow means missing runs — the Daily Monitor shows exactly which days went quiet.

Explore the Daily Monitor →
Coming soon

The quietest failures, made loud

FlowOversee is coming to the Microsoft Store. Try the app in the interactive demo right now — no install, no sign-in, simulated data.

Launch the interactive demo Register your interest →