When an issue closes, and what happens to dismissals

Closing is automatic

You never close a finding by hand. Rabbot closes it the next time it checks the page and the problem is no longer there. There is no “mark as resolved” button, because a button cannot tell whether the page actually works, only Rabbot’s next check can.

What Rabbot actually checks

Each finding is tied to a specific state Rabbot read: a canonical tag pointing somewhere wrong, a missing add-to-cart button, a page answering with an error. On the next check of that page, Rabbot reads the current state again. If it now matches what Rabbot expects, the finding closes. If the page still shows the same problem, or a different one, it stays open or a new finding opens for it.

Why this can take a check cycle

A fix does not close a finding by itself. It closes on Rabbot’s next check of that page, which follows the cadence described in How often Rabbot checks your pages. If you have just fixed something urgent and want to confirm it landed, look at the page yourself the way a shopper would: the same-day check will catch up and close the card once it agrees.

Dismissals evaporate with the fix

If you had dismissed a finding as intentional, the dismissal is not something you also have to clear. It is tied to the finding itself. Once the underlying page matches what Rabbot expects and the finding closes, the dismissal closes with it. There is nothing left over to tidy up. That holds for the two sale-blocking findings Rabbot lets you dismiss as well, a deliberate password gate and a custom purchase flow: 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.

If a closed issue comes back

Closing is not a promise the problem cannot return. If a page that was fine breaks again later, a fresh change, a theme update that reverts your fix, a re-imported product overwriting a correction, Rabbot raises a new finding for it the same way it did the first time. A history of a finding having closed once does not stop it firing again; each check stands on its own.

Seeing what has closed

Findings that have closed drop off your active dashboard, they are not deleted from Rabbot’s record. If you want to check whether something you fixed weeks ago has stayed fixed, the absence of a card for it on your dashboard today means the last check found nothing to raise: either the page is correct, or you dismissed that finding as intentional and it is still muted.