Store is running slowly or shows a 502/504/temporary error
A short-lived 502/504 error or a brief slowdown usually clears up on its own within minutes — retry the page first, then contact support if it continues, since sustained slowness or downtime needs to be checked directly.
Steps
- Retry loading your store after a minute or two — many "down" reports resolve on their own quickly.
- Note whether it's your storefront, your admin dashboard, or both that's affected.
- Check if the slowness is store-wide or limited to one page (e.g. only a specific product or landing page).
- If it persists more than a few minutes, or keeps recurring, contact support with the exact error (502/504/timeout) and how long it's been happening.
- If offers or sections stop appearing on the product page while the store is slow, mention that too — it can be a separate, related issue worth flagging together.
Common problems
- Store shows "502 Bad Gateway" or "Connection Timeout" for an extended periodcontact support right away with how long it's been down; don't assume it will resolve on its own if it's been more than a short while.
- Store and dashboard both feel sluggish, with no clear-cache option visiblethere's no merchant-facing cache-clear button; report the slowness to support with a description of when it started.
- Slowness started right after a platform update or migrationmention the timing when contacting support, since it helps narrow down the cause.
- Offers aren't showing on the product page while the store is also running slowlyreport both symptoms together; they can be related.