Browse documentation
Troubleshooting
Find the next useful check when editing, previews, content, or publishing do not behave as expected.
In this guide
A focused recovery step and the right information to share if you need support.
I cannot select or change an element
Check the editor mode, the selected layer, and the connection state before repeating the action.
- 1
Return to Design
Exit Preview and choose Design if you are in Overview. Use Navigator to expand the section and select the precise child layer.
- 2
Check locks and access
Inspect the layer’s lock state. If the editor is read-only or still connecting, wait for synchronization or ask an administrator to check your access.
- 3
Check the active controls
Open Style. Controls depend on the selection: text, images, containers, component instances, and form fields expose different settings.
My change disappeared or did not save
Check the selected page and design first, then the active breakpoint. A style may apply only at one device size, while you are looking at another.
- 1
Read the visible status
Look for connection, synchronization, validation, or save-error messages. Keep the page open while pending work settles.
- 2
Confirm the target
Check the page, component source, selected layer, and breakpoint. Return to the same target where the edit was made.
- 3
Verify one small edit
Once the connection is healthy, make one small change, finish the edit, wait for pending work to settle, and reopen the page to verify it.
Preview looks different from the editor
Preview runs links and behaviors that are intentionally different from selecting and editing content on the canvas.
| What you see | What to inspect |
|---|---|
| An effect is still or appears at a different moment | Use Preview and exercise its trigger: reload, scroll into view, hover, or press. |
| A layout differs on mobile | Confirm the active breakpoint and any overrides. Check fixed widths and parent padding. |
| A font looks wrong | Resolve any missing-font warning in Style → Text and verify the font asset is available. |
| An image is missing | Confirm processing completed and the selected layer references an available image. |
| The live site shows old content | Check which release is active in production; editor changes need a new release. |
Agent did not make the expected change
Open the intended page and select the target element before retrying.
- 1
Check availability
Read the connection or service notice and check workspace credits. An unavailable provider or exhausted allowance needs to be resolved before another request can run.
- 2
Make the request specific
Name the layer, desired change, breakpoint if relevant, and what should stay the same. Split a broad request into smaller results.
- 3
Inspect the actual result
Check the canvas, Style values, and Preview. Describe the remaining visible difference in your follow-up.
Publishing or promotion is blocked
Use the specific message on the Publishing page or release history to choose your next step.
| State | Next step |
|---|---|
| Checking publish readiness | Wait for checks to finish. Publishing is disabled while readiness is unresolved. |
| Resolve before publishing | Fix the listed issue, then check readiness again. |
| Queued or building | Follow the existing job in Publish Queue or History instead of submitting duplicates. |
| No staging release to promote | Publish staging and wait for a complete release. |
| Approval is missing or stale | Confirm the review points to the exact candidate being promoted and gather current approvals. |
| Reserved domain, no live site | Complete the first production release. A reserved hostname alone serves no website. |
| Domain cannot be primary | Check DNS, routing, and SSL in Domains; all required checks must pass. |
CMS content or form submissions are missing
For CMS, check the entry status, required fields, dynamic route, and selected field bindings. Confirm that you have released the version containing those inputs.
For forms, check the selected Site form, the released page’s connection, and the same form’s inbox. A successful-looking animation is not a substitute for a stored submission.
Get help with a reproducible example
Open Support from the workspace dashboard, or use Contact support in the account menu.
Before you move on
- Include the project name, page, and affected device size.
- Describe the steps, the expected result, and what actually happened.
- Include the exact visible error and the time it occurred.
- Attach a screenshot with the relevant control or status visible.
- Remove API keys, passwords, private content, and share-link secrets before sending.
Screenshots use a local sample workspace.