Alerts
When
A step failing on two consecutive checks opens an incident. One failed check is a blip (a slow CDN, a deploy in progress) and only shows on the timeline. While the incident is open, further failures are counted on it, even when the failing step moves (checkout first, then the cart). The first check that passes closes it.
You get exactly two messages per incident on each channel you switched on: one when it opens, one when it closes with how long the path was broken. Nothing in between.
What the message says
- Which store and which step: "Checkout page is failing".
- The error, as the browser saw it:
HTTP 500,cart is empty after adding the product,add-to-cart button not found,no response within 20 s. - When it first failed and how many checks confirmed it.
- Each step of the failing check with its timing, and a link to the screenshot.
- What to do: reproduce by hand, then look at recent theme, app and payment changes.
Channels
Set them on Alerts in the dashboard.
| Channel | Setting | Notes |
|---|---|---|
| On by default, sent to the account email; change it there | Includes the step list and the screenshot link | |
| Slack | An incoming webhook URL (https://hooks.slack.com/services/…) | Create one in Slack under Apps → Incoming Webhooks and pick the channel |
| SMS | A phone number in international form (+15551234567) | Short: store, step, error, time, link. Standard carrier rates on your side; none on ours |
Daily digest
Once a day (after 07:00 UTC) an email lists, for every store, how many checks ran the day before, how many failed, the 30-day pass rate and any incident of the day with its duration. Switch it off on the Alerts page if you only want incidents.
Theme changes
When the names of your theme's stylesheets and scripts change between two checks, you get one email naming the old and new fingerprint and the theme name when it is visible (Shopify's theme name and id, WordPress's theme folder). If you did not publish a theme, look into it.
Why no alert on the first failure
Checks run from one place with one browser. A single failure is more often the network than the store. Waiting for the second check (30 or 60 minutes later) costs little and avoids waking you for nothing. If you want to know sooner, press Run a check now on the store page.