Where alerts surface
Alerts from data rules appear in three places:
You can also see all triggered records for a single rule by opening Project Settings → Data Rules and clicking into the rule.
An alert on a data point shows up a few seconds after the data arrives or changes. Counts are rebuilt in the background, so a rule’s totals, a batch’s alerts, and alert counts on lists can take a few minutes to catch up.
Alerts on a batch
A batch shows alerts from three places, split across its tabs:
So an alert raised once can appear on every batch downstream of the record. Only alerts from a rule’s current version are shown. Dismiss an alert once and it is dismissed everywhere it appears.
Triage an alert
1
Open the alert
From an Event Detail drawer, batch page, or rule details page, click the alert card. The card shows:
- The alert message
- The rule name and the rule’s effective period
- A See N duplicates link, where the rule clustered several data points together
2
Decide what to do
Three choices:
- Fix the data. If the alert is real, correct the underlying data point or model input. Re-running the calculation re-evaluates the rule; if the data is now in range, the alert is automatically resolved.
- Dismiss the alert. If the alert is a known false positive or doesn’t apply to this record, dismiss it with a reason. The alert is hidden from the active list but preserved for audit.
- Decide a proposed correction. A substitute rule holding its corrections for approval raises a proposal rather than an alert. Approve or reject it from the same drawer; see Approve corrections.
- Adjust the rule. If the alert reveals that the rule itself is wrong (too aggressive, wrong threshold), edit the rule expression. Editing re-evaluates the rule against the project’s data and replaces its existing alerts with the new results. The previous alerts are not kept.
3
Dismiss with a reason
Click Dismiss and provide a reason. The reason is stored alongside the alert and visible to anyone reviewing the rule’s history or the affected report. The card then reads Dismissed by with the name, date and reason, and the rule counts the record as dismissed rather than alerted.
Dismissing an alert does not change the underlying data point or batch. It only changes how the alert is surfaced. The dismissal holds when the data is edited, the calculation re-runs, or you evaluate the period again: the rule does not raise that alert again on the same record. It resets only when the rule gets a new version, for example when you edit its condition or effective dates.
Reviewing rule activity
Open a rule from Project Settings → Data Rules to see its full evaluation history. The Evaluated Records tab lists every record the rule evaluated. It opens filtered to alerts; use the Result filter to show passed or dismissed records too. For Data Points rules, click a record to open the Event Detail drawer. For Batch Calculation rules, click a batch to open the batch preview drawer with the calculation context. The rule’s counts, its Runs tab, and how to revert a run are covered in The rule page.Stopping a noisy rule
If a rule is producing alerts you don’t want to act on:- Shorten the effective period. Set or pull in the Effective to date so the rule stops applying to new records. This saves a new version of the rule, so its active alerts are re-evaluated and any dismissals you made are reset along with them.
- Edit the expression. Tighten or loosen the rule. Editing re-evaluates the rule and replaces its existing alerts with the new results. The previous alerts are not kept.
- Delete the rule. Removes the rule and all of its alerts from the project.
Alerts and reports
Alerts on records included in a report are visible to the report reviewer. To resolve them before submitting a report:- Address the underlying data issue, or
- Dismiss the alert with a reason that the reviewer will see.