Flow Activity Settings
The Settings sub-tab and Schedule Settings control how Blueprint monitors a single Flow. Use them to choose which checks run, adjust thresholds and rule values, set recipients, and mark expected downtime. From the run table on the Overview sub-tab, you can also add runs to the baseline or remove them.
Note: For prerequisites, health statuses and how alerts work, see Flow ActivityFlow Activity.
Opening the Settings Sub-tab
To open the Settings sub-tab:
- Open the Flow and go to Validate -> Flow Activity.
- Select the Settings sub-tab.
Alert Types
The Alert Types section has one switch per check. Switches for checks that don't fit the Flow's type are disabled. Disabling a type stops evaluation and clears any active alert of that type. Past episodes stay in Alert History.
Check | Alerts when | Flow types |
|---|---|---|
Execution Duration | a run's duration is outside the band | All |
Runs Per Day | a day's run count goes above the band, or a completed day ends below it | All |
Queue Items Handled | the items a run handled are outside the band | Consumer, Combined |
Queue Success Rate | a run's success rate is outside the band | Consumer, Combined |
Queue Kickout Rate | a run's kickout rate is outside the band | Consumer, Combined |
Queue Error Rate | a run's error rate is outside the band | Consumer, Combined |
Producer Items Added | the items a run added are outside the band | Producer, Combined |
Run Frequency | time since the last run, not counting excluded time, exceeds the window (24 hours by default. This alert is OFF by default) | All |
Consecutive Failed Runs | the Flow fails a set number of runs in a row (3 by default) | All |
Rate checks count Processed items as successes and Business exception items as kickouts. Generic exception, IT exception and Processing timeout items count as errors. A run that handled 0 items has no rate, so rate checks skip it.
Turning a check off stops its evaluation and clears its active alert. For what happens to the alert and the Flow's health, see Alert History and the Needs Attention IndicatorAlert History and the Needs Attention Indicator.
Note: When you turn Runs Per Day back on, Blueprint evaluates any days it skipped while the check was off. A new alert can appear within an hour.
Thresholds and Baseline
Thresholds set the minimum and maximum for each signal the checks measure. They're listed as Runs per day, then Duration, then the queue signals.
Baseline
Blueprint infers thresholds from a baseline built from the Flow's own run history. The window is the previous 90 full days plus the current partial day.
The baseline leaves out these runs:
- runs flagged as anomalies, unless you add them with Add run to baseline
- runs you remove with Remove run from baseline
- runs that start in a period excluded in Schedule Settings
Inferred and Custom Thresholds
Each bound is Inferred or Custom. A Custom value is one you enter.
- Editing a bound makes it Custom.
- Revert to inferred restores the inferred value. It's available when the bound is Custom and an inferred value exists.
- Rates are percentages, up to 100. Duration uses a timespan format (e.g., 00:01:05). Counts are whole numbers.
An inferred baseline needs at least 10 qualifying runs in the window. With fewer runs and no custom values, the Flow is Awaiting Baseline.
Note: A saved threshold change applies to future runs only. Blueprint doesn't re-flag past runs or redraw the charts, and the save doesn't clear active alerts.
Rule Settings
Run Frequency and Consecutive Failed Runs follow fixed rules and use no baseline. Each value is a whole number of at least 1, and entering 0 saves as 1.
Setting | Description | Default |
|---|---|---|
Run-frequency window | Hours without a run, not counting excluded time, before Run Frequency raises an alert. | 24 |
Consecutive failed runs | Failed runs in a row before Consecutive Failed Runs raises an alert | 3 |
Recipients
The Settings sub-tab also lists the Flow's recipients and shows an Email preview sample. To add recipients and see when emails go out, see Alert NotificationsAlert Notifications.
Schedule Settings
Schedule Settings marks periods when the Flow isn't expected to run. Nothing is excluded by default. You can exclude:
- Weekends, by checking Weekends Preset. Saturday and Sunday are then greyed out.
- Specific days of the week, using Recurring weekday rules.
- Custom date ranges.
A run is off schedule when its start time falls in an excluded period. Off-schedule runs and excluded days don't activate Run Duration, Runs Per Day or queue alerts. Run Frequency doesn't count excluded time toward its window.
To set exclusions:
- Click Schedule Settings in the Flow Activity header.
- Check Weekends Preset, add recurring weekday rules, or add custom date ranges.
- Click Save exclusions.
- Confirm the prompt "Baseline will be recalculated. Do you wish to proceed?"
A toast appears when recalculation finishes, and the tab header lists your exclusions.
A date range is stale when it ends before the baseline window starts. Stale ranges show in red, and Save exclusions stays disabled until you remove them with Remove stale ranges.
A range that starts after it ends shows an error.
What Saving Changes
Saving updates the baseline and the charts. It doesn't re-flag runs. For how saving affects alerts, see Alert History and the Needs Attention IndicatorAlert History and the Needs Attention Indicator.
Off-schedule runs stay in the run table with an Off schedule pill. See Flow ActivityFlow Activity.