Runbooks
Procedures that start from a symptom, collect evidence before changing anything, and end with a check that the fix worked.
| Symptom | Runbook |
|---|---|
| A script or stylesheet is not on the page, or a component never initialises | Asset not loading |
| Cart quantity changes fail, or the drawer shows a stale cart | Cart and line item errors |
| The booking calendar is blank, or shows wrong prices or clinics | Booking calendar issues |
| A popup does not appear, the wrong one appears, or a hidden one shows | Popups not appearing |
| A change needs deploying, or a deploy needs undoing | Deploy and roll back |
Before you start
Work on a preview theme when you can. The store has one live theme and several unpublished ones, and npm run list
shows each theme with its role.
Reproduce the problem in a private window. Much of this theme's behaviour depends on localStorage, cookies and the
Klaviyo profile, so a browser you have already tested in gives misleading results.
Turn on the theme's logger before you collect evidence:
window.enableLogging('*');Then reload. The logger hides all output until you turn it on, so an empty console tells you nothing.
What you will not find in logs
The theme has no server and sends errors to no reporting service. src/@types/global.ts declares window.Sentry, but
nothing in the theme initialises it, so assume nothing collects errors. All your evidence comes from the browser in
front of you.
Shopify admin shows only order records and the theme editor's own history. There is no request log for the storefront.