Failed Runs

Every failed flow. One list. With the error.

Run histories hold the answers — but reading them means opening flows one at a time. FlowOversee adds the triage view: every flow whose last run failed, already collected on one page, error message included.

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.

Hunting failures by hand

  • Last-run outcomes live inside each flow's run history — finding them means opening flows one by one.
  • Failure emails arrive per flow and get buried in the inbox — easy to miss, hard to triage.
  • Answering "what's failing right now, everywhere?" means checking flow by flow.

With FlowOversee

  • One page of every flow whose last run failed — cloud and desktop flows together.
  • The error message sits right in the row — often that alone tells you what broke.
  • Search matches flow names and error text; your include/exclude flow filter applies too.

Failures surface themselves

Open the page and the triage list is already built: which flows failed their last run, what kind of flow each one is, and what the error said. The freshest problems, no digging.

  • Last-run-failed flows for the whole environment, in one list
  • Error text shown inline — search by flow name or by the error itself
  • Live data on every load — never a cached yesterday
FO Nightly Export
Cloud · "Action 'Create_file' failed: request timed out"
Failed
FO Run Macro
Desktop flow · "The machine is unavailable"
Failed
FO Helpdesk Digest
Cloud · "Unauthorized: connection expired"
Failed

From error to fix, fast

A failure row is a starting point, not a dead end. Open the flow's details for its run history and schedule, then jump straight to the maker portal when it's time to actually fix the flow.

  • Details panel: run history, status, schedule, and error details in one place
  • One click to the flow in the Power Automate portal when you need to edit it
  • Pair with background alerts to hear about the failure the moment it happens
FlowOversee notification icon FlowOversee now
Flow run failedFO Nightly Export — Admin Environment
FO Nightly Export
Run history · schedule · error details
Open in portal ↗
Common questions

Failed runs, answered

How do I see all failed flows in Power Automate?
FlowOversee's Failed Runs page lists every flow in the environment whose most recent run failed — cloud and desktop flows alike — with the error message shown right in the row. No opening flows one by one; the failures come to you in a single list.
Can I search failures by error message?
Yes. The Failed Runs search matches both flow names and error text, so you can pull up every flow currently failing with, say, a timeout or an authorization error in one keystroke.
Can I get notified the moment a flow fails instead of checking?
Yes. Turn on FlowOversee's optional background alerts and it sends a Windows notification when a run fails, on the check interval you choose — from every 2 minutes up to hourly. The Failed Runs page is where you land to triage.
Works together

Pairs well with

Alerts

A Windows notification the moment a run fails — so this page is triage, not discovery.

Explore Alerts →

Suspended Flows

The other silent stopper — flows Microsoft suspended, with the reason recorded.

Explore Suspended Flows →

Daily Monitor

Failures are half the story — the Daily Monitor also catches jobs that never ran at all.

Explore the Daily Monitor →
Coming soon

Let the failures find you

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 →