Open the flow in the Microsoft Power Automate portal and read its run history — by default the last 28 days of runs, with status, start time, and duration. The Activity view gathers recent runs across your flows into one feed. And if you would rather have the question answered every day without asking it, FlowOversee's Daily Monitor marks each chosen flow off against its schedule automatically.
When you want to know whether a specific flow ran, its own run history is the source of truth:
"Did it run?" is rarely about one flow once — it is the same handful of scheduled jobs, every morning. FlowOversee's Daily Monitor turns that routine into a checklist that fills itself in: pick the flows that matter, and each day the app marks every one off against its actual run history. A flow that ran shows a check with the run's time and status; a flow with no matching run is flagged as a miss — the quiet failure mode that is otherwise easy to overlook.
The Daily Monitor: every chosen flow checked off against its real run history, day by day.
Templates make it fit real schedules: a weekday list, a month-end list, a critical-only list — each with its own flows, grace rules for jobs that start a little off-schedule, and per-flow time-zone overrides. For the visual version of the same question, the Timeline draws the day's runs as bars on a 24-hour strip: Today shows what has run so far, and Replay shows any past date.
Read more on the Daily Monitor feature page, or try both in the interactive demo — no install, no sign-in.
The common reasons a flow quietly does not run — and how to catch the next miss early.
Read the guide →Every way to hear about a failed flow run — email, in-flow branches, and Windows toasts.
Read the guide →The complete overview: what to watch across your flows and every tool for the job.
Read the guide →FlowOversee is available now on the Microsoft Store. Try the app in the interactive demo right now — no install, no sign-in, simulated data.