--- title: Alert History and the Needs Attention Indicator slug: blueprint/alert-history-and-the-needs-attention-indicator createdAt: 2026-11-06T21:54:17.032Z --- The **Needs Attention** indicator marks a Flow that has at least one active alert. An alert that activated before the Flow's current baseline window doesn't count. The **Alert History** sub-tab lists every alert raised for that Flow, active or cleared. Use them together to see why a Flow needs attention. *** # Needs Attention Indicator On the Flows list, the indicator appears next to each Flow that needs attention, with the tooltip **Needs Attention**. To list only these Flows, filter the list by **Indicator** and choose **Needs Attention**. See **[Flows & Automations](docId\:u1PU2YAQ9rT-vSu48m52W)** On a Flow's page, the indicator appears next to the title. The **Flow Activity** tab header shows the same health status. The indicator updates without a page refresh when health changes. The indicator goes away when every active alert clears. Past anomalies don't keep it showing. For the health status the Flow then shows, see **[Flow Activity](docId\:HyqDjvPWb8LB5Bz9DsuVB)**. For every Flow that needs attention in an environment, see **[Flow Activity (Estate)](docId:_ovEj51Z4oVN5ycDpMmwn)**. *** # Alert History Sub-tab Open a Flow, then select **Validate** -> **Flow Activity** -> **Alert History**. The sub-tab shows one row per alert, newest first. You can't select rows. ### Start Date The text at the top of the sub-tab reads* "Alert history starts \, the date this flow was last modified in Power Automate Desktop before it was imported."* ### Columns - **When** — date and time the alert activated - **Alert type** — check that raised the alert, e.g., **Run Frequency** or **Runs Per Day** - **Observed** — value that activated the alert - **Threshold** — limit the observed value was checked against - **State** — **Active** or **Cleared** pill *** # Alert Lifecycle An alert activates when one of the Flow's checks becomes true. Blueprint then adds a row with the **State** set to **Active**. Each check can have only one active alert at a time. While it is active, the check adds no new rows. Alerts clear on their own. You can't clear or dismiss an alert directly. The row stays, with the **State** set to **Cleared**. | **Check** | **Clears when** | | ------------------------------------- | ---------------------------------------- | | **Consecutive Failed Runs** | any run succeeds | | **Run Frequency** | any run occurs | | **Runs Per Day** | a later completed day is inside the band | | **Run Duration** and the queue checks | a later run is inside the band | A Dataverse sync outage pauses Run Frequency and Runs Per Day but doesn't clear their active alerts. For when Blueprint evaluates each check, and what can cause false alerts or alerts that don't clear, see[ Flow ActivityFlow Activity](docId\:HyqDjvPWb8LB5Bz9DsuVB). When an alert activates, Blueprint sends an alert email. The alert appears in Alert History even when there are no recipients. See **[Alert Notifications](docId\:bRJ6FmAmss4lMAYiQTY1x)**. ### Settings Changes - Turning off a check clears its active alert without sending an email. The row stays in Alert History, and health updates right away. See **[Flow Activity Settings](docId\:Pzyo3nFnI6uFl8gHkZP5i)**. - Saving new thresholds doesn't clear an active alert. The new values apply to future runs only. - Saving **Schedule Settings** doesn't activate or clear alerts. Any change comes from the next run or the hourly job. - Adding a run to the baseline or removing one recalculates the baseline. *** # Retention and Re-import Blueprint doesn't remove Alert History rows over time Re-importing a Flow keeps its Alert History, active alerts and settings :::hint{type="info"} **Important:** Deleting a Flow in Blueprint deletes its Alert History and other monitoring data. A later import of the same Flow counts as a first import. For how a first import sets the start date, see **[Flow Activity](docId\:HyqDjvPWb8LB5Bz9DsuVB)**. ::: *** # Responding to an Alert To find out what caused an alert: 1. Open the **Alert History** sub-tab and find a row with the **Active** pill. 2. Compare **Observed** with **Threshold**. 3. Open the **Overview** sub-tab and find the runs from the time in **When**. 4. Look for values in red font and the yellow **Anomaly** icon in the run table. 5. Check the **Error List** column of any failed runs. Then act on the cause: - If the Flow has a real problem, fix it in Power Automate Desktop. The alert clears when the check passes again. - If a flagged run was valid, add it to the baseline. - If the band is too tight, set custom thresholds on the **Settings** sub-tab. - If the Flow doesn't run on certain days, exclude them in **Schedule Settings**. - If a check doesn't fit this Flow, turn it off under **Alert Types** on the **Settings** sub-tab. For each of these changes, see **[Flow Activity Settings](docId\:Pzyo3nFnI6uFl8gHkZP5i)**.