Flow Failure Instant Push Notification
When any monitored flow fails, send an instant push notification to the admin with the flow name, error, and a link to the run.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
This flow monitors all Power Automate cloud flows in the environment and sends an instant push notification to your mobile device when any flow is detected in a non-running state (suspended, failed, or turned off). It runs on a configurable schedule (default: every 15 minutes) and provides a summary of all problem flows so administrators can take immediate action.
Use Case
Cloud flows can fail or become suspended without warning due to connection issues, throttling, or schema changes. Without proactive monitoring, these failures go unnoticed until users report problems. This flow solves that by pushing real-time alerts directly to the admin's mobile device via the Power Automate mobile app.
The flow is ideal for teams that:
- Instant mobile alerts when flows fail or become suspended
- Reduces mean-time-to-detection for flow failures from hours to minutes
- One-tap deep link to the Power Automate portal for investigation
- Fully configurable check interval via environment variables
Flow Architecture
Recurrence - Every 15 Minutes
RecurrenceFires every 15 minutes (configurable).
Initialize varEnvironmentName
Initialize variableReads the flowlibs_PAEnvironmentName environment variable into a string variable.
Initialize varCheckInterval
Initialize variableReads the flowlibs_FlowCheckIntervalMinutes environment variable into an integer variable.
Initialize varFailureCount
Initialize variableInteger counter that starts at 0; incremented for each non-running flow.
Initialize varFailureSummary
Initialize variableString accumulator used to build the failure details body for the push notification.
List All My Flows
Power Automate Management - ListMyFlowsCalls the Power Automate Management connector ListMyFlows action for the target environment ID.
Filter Flows Not Running
Filter arrayKeeps only flows where properties/state is not equal to 'Started' (i.e., suspended, stopped, or failed).
Loop Through Failed Flows
Apply to eachFor each problem flow: increment varFailureCount and append the flow's display name and state to varFailureSummary.
Check If Any Failures Found
If conditionIf varFailureCount is greater than 0, compose the notification text and send a push notification; otherwise do nothing.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_PAEnvironmentName | String | <your-tenant-id> | The environment ID (GUID) for Power Automate Management API calls. Set this to your target Power Platform environment's ID. |
| flowlibs_FlowCheckIntervalMinutes | String | 15 | How many minutes between checks — keep this aligned with the Recurrence trigger interval. |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Power Automate Management | shared_flowmanagement | ListMyFlows (Retrieves all flows in the target environment) |
| Notifications | shared_flowpush | SendNotification (Pushes alert to the Power Automate mobile app) |
Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.
Customization Guide
Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.
- Deploy to another environment
- Import the solution into the target environment, update flowlibs_PAEnvironmentName to the new environment ID, set up connection references for Power Automate Management and Notifications, then turn the flow on.
- Change check frequency
- Edit the Recurrence trigger interval and update flowlibs_FlowCheckIntervalMinutes to match so the body text stays accurate.
- Exclude specific flows
- Add a second Filter Array after the first one to exclude flows by display name pattern (e.g., test or sandbox flows you don't want to alert on).
- Add email notification
- Add a Send Email action alongside the push notification inside the If condition for dual-channel alerts.
- Add Teams notification
- Add a Post Message to Teams action to alert an entire team channel in addition to the mobile push.
Key Expressions
The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.
EXPR.01Read env var
Reads the target environment ID from the environment variable.
EXPR.02Filter non-running flows
Used in the Filter Array — keeps any flow whose state is not 'Started'.
EXPR.03Get flow name in loop
Reads the current flow's display name inside the Apply to each loop.
EXPR.04Get flow state in loop
Reads the current flow's state inside the Apply to each loop.
EXPR.05Check failure count
Condition expression — only sends the push notification when at least one non-running flow was found.
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.