Help & Guide/Connected store
Store Health
Open in appCPU, RAM, disk, DB, and render time from the store self-check.
Store Health charts the last days of origin self-check samples: CPU %, memory %, disk %, database ms, page render ms, and 1-minute load. WooCommerce 1.5.2+ and Magento / Adobe Commerce 1.3.1+ send a sample on each ~5-minute sync. The page refreshes about once a minute. Gauges use your Settings lines (amber past warn, red past crit). Red CPU/RAM/disk is a saturation heads-up — the store is only marked down if pages/DB stall, origin 5xx/524, or 1-minute load crosses your down factor.
If sync is missing, overdue (about 15 minutes), or arriving without origin metrics, Store Health and Home show a banner with what to do: Sync Now in WordPress or Magento admin, then open Extension Health.
Shopify and BigCommerce cannot send origin CPU/RAM/disk. This page says so instead of leaving blank charts. Their storefront is still watched by the auto-created HTTP monitor and optional synthetic browser checks.
Load (1m) is compared with CPU core count. Defaults are warn at 8× cores and down at 16×. You set both factors under Settings → Origin health.
A visitor heartbeat only proves PHP is still answering. It does not clear a CPU, RAM, disk, stall, or load incident — that waits for the next healthy self-check on sync.
Related
- Self-check thresholdsWarn and down lines for CPU, RAM, disk, DB, render, and load (× cores).
- How origin health works by platformWhat CPU, RAM, disk, and load mean — and which stores can send them.
- When a page asks for the moduleModuleGate pages stay empty until the store plugin has synced.
- Extension HealthLast sync, extension version, and whether push is alive.
- Synthetic browser checksOptional real-browser load of the storefront, off until you turn it on.
Still stuck? Open a support ticket.