Troubleshooting

Most problems have one of a handful of causes. Work through these before assuming something is broken for good.

First: is it us or you?

Open the status page. If a component is degraded, waiting is usually the fix.

The preview will not load

• Reload it.
• Open it in a new tab. If it loads there, the problem is the panel, not the app.
• If a change just landed, it may still be applying. Wait a moment, then reload.

A publish failed

The error message usually names the step that failed:

• A check failed: something does not compile, or QA or Security found a blocking problem. Ask the builder to fix the specific error.
• A service was unreachable: retry. If it happens twice, check the status page.

Your live app keeps running while a publish fails.

Changes are not appearing

• Publish. Preview and live are separate by design.
• Hard-reload the live page, because browsers cache aggressively.
• Check you are looking at the right address. A custom domain may still point somewhere else.

A form does nothing

• Look for an error message near the field.
• Check the browser's network activity. A request that is rejected often means a permission rule is blocking it.
• Sign in as the right role.

Email is not arriving

• Was the sending domain verified? Unverified domains land in spam or vanish.
• Check the spam folder and any team-wide filter.
• Send to a different mailbox to rule out the recipient.

The live app misbehaves

Use Doctor to diagnose the root cause, or roll back while you investigate.

Data looks wrong

Code versions do not restore data. Describe what you expected and what you see, with a screenshot, and ask for a check before changing anything.

Still stuck

Say what you expected, what happened, and what you already tried. That three-line message is enough for the builder to investigate, and for a person to help you quickly.