Mark it expected
The check keeps running, but your note is placed in the agent's prompt for that check on that table, with a standing rule: if what it sees now matches a recorded expectation, do not report it.
Feedback on alerts and tables is stored and passed on as context to future agents to that they learn from previous events.
Mark expected
orders · Volume
1,900 rows yesterday; weekday baseline is about 10,400.
Black Friday backfill runs the following Monday.
Mute
customers · Null-rate
email is 38% null today; baseline is 2%.
Mark an alert as expected or mute it to reduce noise and only get alerted of issues that matter to you.
The check keeps running, but your note is placed in the agent's prompt for that check on that table, with a standing rule: if what it sees now matches a recorded expectation, do not report it.
Compeltely supress alerts for a table or alert until a specific date.
For every custom check, how many days it ran and how many findings it produced over the last week.
Whether the check is muted right now, how much suppressing feedback it has, and your expected notes word for word.
A check whose findings you keep marking expected is firing on normal behaviour, so the planner narrows or retires it. Anything you disabled or muted is never proposed again.