Why Rabbot warns you once

One alert per catch

When Rabbot finds a new problem, it tells you once: one email on the day it was caught, plus one Slack post if the finding is critical and you are on a paid plan with Slack set up. Slack receives critical catches; everything below critical stays in email and the weekly digest. For most findings that is the end of it, with no follow-up the next day to say the problem is still there. The dashboard already shows every open finding at any time, so a daily reminder would just repeat what you can already see, and would train you to stop reading it.

There is one exception, and it is deliberate. A finding that is blocking sales while it stands does get chased: Rabbot comes back on a widening schedule that settles into a daily reminder until the problem clears. Silence through an outage would be the worse mistake.

Why not chase you every day

An alert only works if it means something when it arrives. If Rabbot pinged you daily for every open issue, the useful ones would get lost in the routine ones, and the alert channel would turn into noise you learn to ignore. Warning once, then leaving the record on the dashboard, keeps each alert worth opening.

When you do hear again

You are not left with only one chance to notice something. If a problem closes and then reopens soon after, within an hour for a critical finding or within a day for a warning, Rabbot holds back a fresh alert: the reopening stays on your dashboard and the weekly digest covers it, so a briefly unstable page does not spam you. If a problem closes properly, and the same thing breaks again later, that counts as a new incident and you get a new alert for it. Warn-once means once per problem, not once ever.

If you would rather not hear about something again

Some findings are not worth an alert to you, a redirect you added on purpose, say, that Rabbot reads as a change. For those, use Dismiss as intentional on the finding in the dashboard. It stops future alerts for that specific change without marking it as fixed. The card drops off your dashboard once you dismiss it, and nothing about the page changes: the state you dismissed is still exactly as it was. If the page is later changed back or genuinely repaired, the finding closes on its own and the dismissal drops away with it. See Dismissed change types for what dismissing does and does not cover.

The short version

Rabbot tells you once when something breaks, stays quiet while it stays broken unless it is blocking sales, and tells you again if it happens again after being fixed. The dashboard is always there for the full picture in between.