The Flow Activity tab shows run data and health for the current PAD Flow, provided it has run in the connected environment. Use it to check that the Flow still does meaningful work, and to find failed and anomalous runs.

The tab header shows the Flow's health status, Flow type and exclusions, and opens Schedule Settings. Below the header are three sub-tabs:

For alert emails, see Alert NotificationsAlert Notifications. For the health and activity of every Flow in an environment, see Flow Activity (Estate)Flow Activity (Estate).

Note: Alert emails need at least one recipient on the Flow or its environment. See Alert NotificationsAlert Notifications.

Blueprint sets each Flow's type from the queue actions it contains. It detects the type on Flow Import and on each Dataverse Synchronization. The type decides which charts, run table columns and checks apply to the Flow.

The tiles and charts cover the baseline window, which is the previous 90 full days plus today.

Charts and checks count days in the environment's Server Time Zone, which is UTC by default.

Use the date-range picker to narrow every chart to part of that window. You can pick only dates inside the window. Narrowing the view never changes baselines, anomaly flags or health. Click Reset to 90 days to show the full window again.

The tiles at the top show data for the entire 90 day range and ignore the date-range picker.

A tile with no data shows a dash. Schedule Settings exclusions don't change the tile numbers.

Which charts appear depends on the Flow type.

On the scatter charts, each dot is the median value for one day.

Successful runs per day and Failed runs per day have no thresholds and raise no alerts.

The All Flow Activity table lists the Flow's runs, one row per run. Its columns depend on the Flow type.

Values outside the Flow's thresholds show in red font.

Runs that start in an excluded period show an Off schedule pill. Their text and background are grey, and their checkbox is disabled. Blueprint hides their anomaly icon and Included or Excluded pill, and shows them again if the schedule changes.

To add a flagged run to the baseline or remove a run from it, see Flow Activity SettingsFlow Activity Settings.

In the run table on the Overview sub-tab, you can add a flagged run to the baseline or remove any run from it.

To include or exclude runs:

A toast appears when recalculation finishes. Added runs show an Included pill, and removed runs show an Excluded pill.

The dropdown offers only the action that applies to the selected runs. To undo, select the run and choose the opposite action, which removes the pill.

Blueprint stores each decision per run, and every user sees it. An added run keeps its anomaly flag.

An anomaly is a permanent flag on one run, or one day, whose value fell outside its thresholds.

An alert is a check that is true of the Flow right now. Each check has at most one active alert per Flow. The alert clears on its own when the condition no longer holds.

Run Frequency and Consecutive Failed Runs have no thresholds, so they raise alerts but never anomalies. When an alert activates, Blueprint adds a row to Alert History and emails the recipients. See Alert History and the Needs Attention IndicatorAlert History and the Needs Attention Indicator and Alert NotificationsAlert Notifications.

For the nine checks, what each one alerts on and which Flow types it applies to, see Flow Activity SettingsFlow Activity Settings.

Saving thresholds or Schedule Settings doesn't re-flag past runs. For how settings changes affect alerts, see Alert History and the Needs Attention IndicatorAlert History and the Needs Attention Indicator.

Flow Activity uses runs from the date the Flow was last modified in Power Automate Desktop before its first import. Blueprint sets this start date at first import and never moves it. Alert History shows the date at the top.

Runs since that date count toward the baseline, so a Flow can have a baseline on its first day. If you choose a longer run history when you import the Flow, the tab still shows only runs since this date.

Sync counts as down when no sync completes within the sync interval plus a buffer. A banner then shows on Tools -> Flow Activity and on the Flow Activity tab of each Flow in that environment.

Run Frequency and Runs Per Day pause for that environment until sync recovers. Other checks are unaffected, and active alerts stay active. On recovery, the banner clears and Blueprint evaluates the missed runs and days.