For one flow, open its details page and use Run history to inspect individual executions; use Analytics to spot trends. To find failures across an environment, use the Power Platform admin center’s Monitor experience. For longer-term records or deeper telemetry, consider Dataverse flow-run history or Application Insights. These views have different scopes and refresh or retention limits, so choose the one that answers your operational question.
Choose a monitoring view for the question you have
| Method | Best for | What it shows | Important limit |
|---|---|---|---|
| Flow details and Run history | Investigating one flow | Individual runs, action status, durations, and errors | Standard run-history data is available for 28 days by default. |
| Per-flow Analytics | Trends for one flow | Run volume, success and failure rates, execution time, and bottlenecks | Rolling 30-day summary; refreshes approximately every 24 hours, not in real time. |
| Power Platform admin center Monitor and analytics | Environment-level oversight | Cross-flow failures and usage patterns | Admin-oriented; available reports and permissions depend on the view. |
| Dataverse FlowRun records | Queryable run metadata and longer-term retention | Status, start and end times, duration, trigger type, error code, and error message | Requires configuration; retention settings and feature limitations apply. |
| Application Insights | Deeper diagnostics and custom alerts | Flow, trigger, and action telemetry | Requires environment-level setup; confirm eligibility and licensing for your environment. |
| Purview audit logs | Governance and change tracking | Flow lifecycle and permission-change activity | Does not show individual runtime runs, action executions, or connector calls. |
The distinctions matter: an analytics report is for trends, not immediate incident detection; an audit log answers who changed a flow, not whether a particular run succeeded. Microsoft’s monitoring overview was marked last updated June 1, 2026. Availability, permissions, licensing, and tenant settings can vary.
Inspect an individual flow and its run history
- Open the flow in Power Automate and go to its details page.
- Open Run history and select the execution you need to investigate.
- Review the overall status, then expand the actions to inspect their status, duration, inputs or outputs when available, and any displayed error.
- Record the run time and the first action that actually failed before changing the flow. This helps distinguish the original fault from later actions marked failed as a consequence.
Run history is the right starting point for a specific execution because it exposes action-level detail. Microsoft documents 28 days as the default availability window for standard run data. If you need records beyond that period, plan a separate retention approach rather than assuming the ordinary history view is an archive.
Use Analytics for one-flow trends, not live alerts
Open the flow’s Analytics view to look for changes in run volume, success or failure rates, and execution time. It can help you see whether a flow is becoming slower or failing more often, and identify potential bottlenecks across its recent runs.
#1 Best Overall
Microsoft describes this as a rolling 30-day run-history summary that refreshes approximately every 24 hours. It is therefore not a real-time operations dashboard, and a recent incident may not appear in the report immediately. Microsoft also notes that this analytics feature is not currently available in government and sovereign clouds. Check your environment’s availability before making it part of an operational procedure.
Monitor failures across an environment
When the question is “Which flows failed?” rather than “What happened in this run?”, use the Power Platform admin center’s Monitor experience. Microsoft describes Monitor as the route for seeing all failed runs, including failures that are not covered by per-run email alerts. Admin-center analytics can also help with environment-level run and usage patterns; the documented environment analytics period includes the last 28 days of run history.
Use the admin experience for cross-flow oversight, then open the affected flow’s run details for action-level diagnosis. Reports and access vary by view and role, so make sure the people expected to investigate can reach the relevant environment and details.
Configure failure notifications with realistic expectations
Failure emails are useful prompts to investigate, but they are not a complete or guaranteed immediate alerting system. Microsoft says per-run alerts are sent for some known, fixable issues. General action failures and failures that cascade from an earlier problem may not produce an email. A per-run alert can also be subject to a 28-day cooldown for the same flow, and alerts may need to be enabled in the flow’s settings.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- Check the flow’s settings if you expect per-run notifications and none arrive.
- Use the admin-center Monitor experience for environment-wide failed-run visibility instead of relying on email alone.
- Use Microsoft’s weekly digest as a summary of failures across environments, not as a substitute for timely incident response.
Diagnose a failed run or an empty history
Find the first real failure
In a failed execution, inspect the earliest action that actually failed and read its run details and error. Later dependent actions can also be marked failed because a prerequisite did not complete; those statuses do not necessarily mean those later actions ran and failed independently. Start with the original failing action, then check whether the flow’s conditions, inputs, connector response, or downstream logic explain the error.
Separate trigger, action, and logic problems
- No run appears: Confirm that the triggering event occurred. Then check whether trigger conditions filtered it out. A flow can be saved successfully without every expected event creating a run.
- The run starts but an action fails: Open that action’s details and use the displayed error and available inputs or outputs to investigate the operation that failed.
- Later actions show failures too: Trace dependencies back to the first failed action before treating each downstream status as a separate problem.
- A run seems absent from an older date: Check whether it is outside the standard 28-day run-history availability window or whether you have an appropriately configured longer-term record source.
Microsoft’s troubleshooting guidance includes the symptom “Your flow saved successfully, but no runs appear in run history.” The useful first distinction is whether the trigger fired at all, rather than assuming a successful save means an execution should exist.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Extend retention and add observability when needed
Dataverse flow-run history
For queryable run metadata or longer-term history, Microsoft documents cloud-flow run history stored as Dataverse FlowRun records. The records can include start and end time, duration, status, trigger type, error code, and error message. Configure retention for your needs and review current feature limitations; the available information does not establish one retention duration that applies to every tenant.
Application Insights
Application Insights, part of Azure Monitor, can receive flow, trigger, and action telemetry at the environment level. Microsoft describes it as an option for examining performance, failures, and usage, and for defining custom alert conditions. It requires setup and is a different, deeper observability approach than checking a flow’s run-history page. Confirm eligibility and licensing in your tenant before designing around it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
Purview audit logs
Use Purview when you need governance evidence about flow creation, edits, deletion, or permission changes. Microsoft explicitly distinguishes those audit events from runtime monitoring: Purview does not include individual runs, action executions, or connector calls. For execution tracking, use run history, admin-center analytics, Dataverse run records, or Application Insights as appropriate.
Match access to the troubleshooting task
The Power Automate Operator role provides visibility into cloud-flow run metadata through Dataverse, but does not provide the detailed cloud run history served by the runtime. Operators cannot see per-action inputs and outputs, expression evaluation results, retry details, or the full trigger payload; they also cannot resubmit or cancel a cloud run. If an operations role must diagnose action-level failures, verify that its permissions support that work rather than assuming metadata access is equivalent to full run-history access.
Or skip the browser setup
ScreenshotNeo is a website screenshot API, not a Power Automate run monitor. It can be useful when a runbook or automation also needs a screenshot of a public web page. One GET request captures a page; see the ScreenshotNeo API documentation for options.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers state the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000, and every feature is on every plan. Visit ScreenshotNeo for product details, or sign up free for 1,000 screenshots a month with no card.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Operational checklist
- Use Run history to investigate an individual execution and identify its first actual failure.
- Use Analytics for one-flow trends, remembering its approximate 24-hour refresh.
- Use admin-center Monitor when you need a cross-flow view of failed runs.
- Do not treat failure emails as exhaustive; check alert settings and use broader monitoring for coverage.
- Choose Dataverse or Application Insights when the retention, query, telemetry, or alerting need exceeds the standard views.
- Use Purview for lifecycle and permission auditing, not execution history.
- Verify that each investigator’s role grants the detail the incident requires.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
