What emails will AccessLint send about my flows?
Flows are designed to be quiet: silence means the journey works and nothing new was found. When something does change, AccessLint sends at most one email per run, to every member of the account (at each member’s login email, or their GitHub email if that’s all we have). Every alert links to the run report, where you can read the results and triage anything new.
The three alerts
New violations found — a run completed and found violations that aren’t in the flow’s baseline. These are the regressions the flow exists to catch. The email lists them grouped by rule, most severe first — the top 10 rule groups in full, then a count of the rest — each tied to the step where it was found.
Flow is broken — a step failed, so the journey itself no longer completes; a checkout that can’t be finished is a bigger problem than any single violation on it. The email includes a screenshot of where the run stalled. This alert is edge-triggered: you get one email when the flow first breaks, not one per broken run, and a passing run re-arms it. If the same run also found new violations, they’re folded into this one email rather than sent separately.
Structure changed — most of the page structure the baseline was anchored to changed at once, which usually means a redesign or rebuild rather than a wave of real regressions. Instead of a flood of per-violation alerts you get one notice, and the next run re-anchors the baseline against the new structure. If you didn’t ship a redesign, take a look at the run.
When you won’t get an email
- Dry runs never email — they haven’t seeded a baseline yet.
- Runs with nothing new, even if known violations remain in the baseline.
- Still-broken runs — the broken alert fires when the flow breaks, not on every run while it stays broken.
- Known and dismissed violations never re-alert.
- Runs that failed before completing — for example, when AccessLint couldn’t sign in. The flow’s page shows what happened, and a sign-in failure pauses the flow so it doesn’t keep failing against a login wall.