Dismissed change types

What the list shows

Open Settings and find the Dismissed change types card. It lists the change types muted across your whole store, one row each, with a control to lift any of them again. A fresh account shows “Nothing dismissed yet.” until the first store-wide dismissal is made.

How something lands on this list

You do not dismiss anything from Settings itself, and there are two ways to mute a change type. Only one of them lands on this card.

The everyday one is per page. Open the affected pages under a finding on the dashboard and choose Dismiss as intentional on the row for the page in question. That mutes the change on that page, and it lives on the finding rather than on this card.

The other is store-wide, made by an agent through Rabbot’s MCP server rather than from the dashboard. It covers the change type everywhere on your store, and that is what this card lists.

What dismissing actually does

Dismissing mutes future alerts for that specific finding. It does not mark the finding as fixed, and it does not pretend the problem went away: the dismissal is a note that you meant it, nothing more. A dismissal on a single finding clears itself when the problem is repaired, so if the same thing breaks again later, Rabbot alerts you as normal. A store-wide dismissal is different: it stays in force until you re-enable that change type from the Dismissed change types card in Settings.

What you cannot dismiss

A small set of sale-blocking findings do not offer a dismiss option. Leaving one of those unaddressed costs orders, so Rabbot always alerts on it rather than letting it go quiet. Two of that set are documented exceptions, because both are things a merchant does on purpose: a storefront behind a deliberate pre-launch password gate, and a product page running a custom purchase flow instead of a standard add-to-cart form. Those two accept a dismissal, and a single-finding dismissal is reset if the finding is later repaired, so a genuine break after that still reaches you. Findings that erode traffic over time rather than blocking a sale outright, including some Critical-level ones, do accept dismissal, since those are the cases where a merchant genuinely knows better than the check.

Why this matters for your alerts

Every dismissal you make is an honest edit to what Rabbot warns you about, not a way to hide a problem. This card is the record of the store-wide edits, and a per-page dismissal sits with the finding it belongs to. Either way a quiet inbox has an explanation you can read back: nothing is wrong, or the things Rabbot is not mentioning are the ones you told it to leave alone.