--- title: Flow Activity (Estate) slug: blueprint/flow-activity-estate docTags: kEeQ6vT7FPx-7PjzNcWzO createdAt: 2026-04-17T18:28:52.008Z --- :::CtaButton{label="๐Ÿ”ต ALC" openInNewTab="false"} ::: Open Flow Activity by clicking **Tools** in the main toolbar at the top of ALC, then choosing **Flow Activity**. The Flow Activity page shows the health and run activity of every PAD Flow imported into ALC from the selected environment. Use it to find Flows that need attention, check run volume and failures, and open any Flow's Flow Activity tab. The page covers the environment selected in the Environment Switcher at the top right of ALC. See **Environment Switcher**. Health and alerts cover only Flows imported from a Dataverse environment. *** # Tiles | **Tile** | **Description** | | ------------------- | --------------------------------------------------------------------------------------------------------- | | **Healthy** | Flows with usable thresholds and no active alert | | **Needs Attention** | Flows whose health status is Needs Attention | | **Alerts** | alerts that activated in the last 7 days, including ones that have since cleared; each alert counts once | Alerts that activated before the baseline window began don't count toward **Needs Attention**. *** # Needs Attention Table The **Needs Attention** table lists each Flow whose health status is Needs Attention - **Flow** โ€” name of the Flow; click to open its Flow Activity tab - **Reason** โ€” check and direction of the active alert, or a count such as "2 alerts active" when more than one is active - **Observed vs. expected** โ€” value that activated the alert and the threshold it crossed; the check names when more than one alert is active - **Time of Alert** โ€” date and time the alert activated; the latest activation when more than one alert is active Time of Alert is when the alert activated, which can be later than the last run. A Run Frequency alert activates because a run is missing. Rows are sorted by most recent alert, newest first, and you can't change the order. The table shows 10 rows per page. A Flow leaves the table on its own when its last active alert clears. The Flows list marks the same Flows with the **Needs Attention** indicator. To find what caused an alert, see[ Alert History and the Needs Attention IndicatorAlert History and the Needs Attention Indicator](docId:75aUZSK98PLhtUjmw_VLr). *** # Activity The Activity section shows run counts and charts for all Flows in the environment. It covers the baseline window, and the page has no date-range control. Activity counts every run, including runs that start in periods excluded in Schedule Settings. Baselines leave those runs out, so Activity can count runs that a Flow's baseline ignores. A banner that begins "Activity counts", between the run volume chart and the **All Flows** table, explains this. ### Activity Tiles | **Tile** | **Description** | | ------------------------- | ----------------------------------------------- | | **Total Flows** | imported Flows with run data in the environment | | **Total Runs** | runs across all Flows | | **Total Successful Runs** | successful runs, shown in green | | **Total Failed Runs** | failed runs, shown in orange | ### Charts | **Chart** | **Description** | | -------------------------------- | ----------------------------------------------------------- | | **Top 5 Failed Flows** | the five Flows with the most failed runs; hover for details | | **Top 5 Errors** | the five most common error messages; hover for details | | **Run volume across the estate** | all runs across every Flow, by date | **Warning:** Local runs don't capture queue time, execution duration, CPU or memory, so these four charts can't include them. *** # All Flows Table The **All Flows** table lists each Flow in the environment with its baseline, health and recent failures. - **Flow** โ€” name of the Flow; click to open its Flow Activity tab - **Baseline** โ€” how the Flow's thresholds are set; **Inferred**, **Custom** or **None** - **Health now** โ€” the Flow's health status as a pill; **Healthy** (green), **Needs Attention** (red) or **Awaiting Baseline** (grey) - **Failed ยท 90d** โ€” failed runs in the last 90 days - **Last run** โ€” date and time of the Flow's last run The page doesn't list individual runs. Click a Flow's name to open its Flow Activity tab, then use **Overview** to see its runs or **Alert History** to see its alerts. ### Baseline Values | **Value** | **Meaning** | | ------------ | -------------------------------------------------------------------------------------------------------------------------- | | **Inferred** | every threshold is inferred from the Flow's own run history | | **Custom** | at least one threshold is Custom, either a value you entered or one Blueprint prefilled; the others can still be inferred | | **None** | too few qualifying runs for an inferred baseline, and no custom thresholds | For the run minimum, how Blueprint infers thresholds and how to change them, see **Flow Activity Settings**.