Help & Guide/Account, plans & support
Synthetic browser checks
Open in appOptional real-browser load of the storefront, off until you turn it on.
- 1Open Settings → Origin health.
- 2Turn on “Run synthetic browser checks for this organization.”
- 3The scheduler loads each connected store URL in a headless browser. A 5xx/524 or load failure opens an incident; a passing load clears a synthetic incident.
- 4Leave it off if your CDN often challenges our IP. Inconclusive challenges never open incidents.
This is not checkout Playwright (Transactions). It is a storefront page load through the same edge a shopper hits, so it can catch worker-exhaustion 524s that the HTTP probe (blocked or challenged) and the in-store self-check can miss.
Off by default for every tenant. The Settings toggle is the normal path. Operators can still kill it for the whole process with SYNTHETIC_ENABLED=0, or force it on for every org with SYNTHETIC_ENABLED=1.
Related
- How origin health works by platformWhat CPU, RAM, disk, and load mean — and which stores can send them.
- Store HealthCPU, RAM, disk, DB, and render time from the store self-check.
- UptimeAll probes, connected stores, pause and delete.
- SettingsAlerts, origin health, checkout, planned work, team, and advanced detectors.
- Create a checkout testAdd a Playwright flow so a broken cart is caught before shoppers.
Still stuck? Open a support ticket.