Error playbook
Find the exact Runner error message, understand what failed, and follow safe recovery steps before retrying.
Copy the error you see in Runner and search for it here to find the next safe step. You can also paste the message into Runner chat and name the screen and action that produced it.
Find your error
Entry path: Documentation → Help and reference → Error playbook, or use documentation search with the error text.
| Where you saw the error | Messages and recovery steps |
|---|---|
| Versions, preview, Design Mode, publishing, or domains | Build, preview, and publishing errors |
| Creative Studio, design files, image generation, or Media Library | Creative and media errors |
| Sign-in, workspace, account, billing, chat, tasks, or attachments | Account and chat errors |
| Products, imports, orders, connected apps, analytics, SEO, or automations | Store and app errors |
Search the exact wording first. If a name, number, file, or provider detail changes within the message, search the fixed part and the feature name. For a translated error without a match, ask Runner to search the English equivalent. A message such as “Something went wrong” needs the screen and attempted action to identify the right instructions.
Before you retry
- Keep any unsent text or unsaved edits, and note the error and the action that came before it.
- Check whether the original action is still running or already completed. For payments, imports, publishing, invitations, and other actions outside the current screen, inspect the resulting record or destination before repeating it.
- Follow the matching guide’s recovery steps. Correct missing input, access, or connection requirements before trying again.
- Confirm the expected result in the affected screen. A dismissed toast, a loaded preview, or a successful connection does not confirm that a separate store operation completed.
- If the same error returns after the documented recovery, stop repeating the action and contact Support.
Example: a version will not display
Couldn’t show this version — try again or pick another.
Runner could not load the selected historical preview. Open the version preview recovery steps to retry the preview or choose another version. Restore changes your working version; it is not a preview troubleshooting step.
Ask Runner for help
I see “[paste exact error]” in [screen] after [action]. Find this error in the documentation, explain what I can do next, and tell me how to check that it worked. The original action is [still running / completed / failed / unknown].
Do not include passwords, one-time codes, API keys, payment credentials, or customer information. If you need support, include the project or conversation link, the time, the screen, the exact error, and which recovery step failed. Remove private information from screenshots.
When the message is not listed
Some errors include text returned by a connected service, so their wording varies. A generic message does not identify the cause. Use the relevant feature guide, check the service’s visible connection or operation status, and contact support if the outcome is unclear. Do not disconnect a working app, delete a store, restore a version, or repeat a payment merely to clear an error.
The steps in this reference describe the conditions supported by Runner’s current interface. Some errors occur only with a particular provider, account role, store type, or failed operation; their presence here does not mean your store has that problem.