How do I manage known violations?

A Flow alerts only on violations that are new compared to its baseline. The Known violations card on the flow’s page is that baseline — the record of everything the alarm currently ignores. It isn’t a backlog to drive to zero; its job is keeping the alarm honest, so every alert you do get is worth acting on.

How violations enter the baseline

Approving a dry run seeds the baseline with everything the run found.
After that, each new violation alerts once — in the run report and by email — and is then absorbed into the baseline as active, so later runs don’t re-notify you. No acknowledgment step is required.

Active violations resolve themselves: when a run no longer finds one, it leaves the baseline automatically and the run reports it as resolved.

Reading the list

Violations are grouped by rule and ordered most-severe first (critical → serious → moderate → minor). Expand a group to see each instance’s selector and, where one exists, a screenshot crop of the element in context on the page.

Dismissing a violation

Dismiss mutes a violation permanently: it stays in the baseline, never alerts again, and — unlike an active violation — is never auto-resolved. Use it for findings you’ve judged not worth fixing: a third-party widget you can’t change, a rule that’s noise for your stack.

You can dismiss wherever you’re standing:

On the run report — each instance under New violations has a Dismiss control, right where the alert email lands.
On the flow page — instances in the Known violations card can be dismissed the same way.
While approving a dry run — each seed rule group offers a Dismiss all N instances checkbox, applied when you approve. This is the right tool when onboarding surfaces a flood of one rule you’ve decided to mute.

Every dismissal is recorded with who dismissed it, when, and an optional one-line reason. The reason is optional by design, but worth writing: it’s what makes the mute auditable later, and the trail doubles as an attributed record of remediation decisions.

Auditing and reversing dismissals

Dismissed violations collapse into a Dismissed (N) section at the bottom of the card — the count is deliberate, since it measures how much the alarm is ignoring. Each row shows the dismissal record and when the violation was last seen: “last seen 3 days ago” means the mute is still suppressing something real on your site; a violation not seen for months means the mute is moot.

Click Re-enable to reverse a dismissal. The violation returns to the active list — where it resolves automatically once it stops appearing — and the original dismissal record is preserved, so changes of mind stay auditable.