Skip to main content
When a data rule’s expression matches a record, Mangrove raises an alert. This page covers where alerts surface, how to triage them, and how to act on them without losing audit history.

​
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.

​
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, or the rule name where the rule has no message
  • The rule name and the rule’s effective period
  • A See N duplicates link, where the rule clustered several readings together
The expression itself is on the rule detail page, in Project Settings → Data Rules, with its variables highlighted.
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.
  • 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 alert and provide a reason. The reason is stored alongside the alert and visible to anyone reviewing the rule’s history or the affected report. Dismissed alerts appear with a dismissed tag rather than fail.
Dismissing an alert does not change the underlying data point or batch. It only changes how the alert is surfaced. If the data is recalculated and the rule still matches, a fresh alert can be raised.

​
Reviewing rule activity

Open a rule from Project Settings → Data Rules to see its full evaluation history:
  • Alerted Records — every record the rule currently matches, with status (fail, pass, dismissed), date range, tracking ID, and source.
  • Test rule — re-run the expression against recent project data without saving anything new. Useful when you want to gauge whether a rule is still firing as expected.
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.

​
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.
Choose shorten the effective period when the rule has served its purpose for past data, edit when the threshold or condition needs tuning, and delete when the rule is no longer relevant to the project at all. The first two both reset the rule’s dismissals, so do your triage after the change rather than before it.

​
Alerts and reports

Alerts on records included in a report are visible to the report reviewer. To resolve them before submitting a report:
  1. Address the underlying data issue, or
  2. Dismiss the alert with a reason that the reviewer will see.
Either path produces an audit-friendly record of how the issue was handled.