Back to help
Troubleshooting
Troubleshoot generation, publishing, and domain issues
Collect the right evidence when something fails so the issue can be diagnosed quickly and safely.
step 1
Start with the user-visible symptom
A precise report is faster than a large log dump. Name the page, action, expected result, and actual result.
- Record the route or screen name.
- Include approximate time and timezone.
- Describe whether the issue affects one workspace, one domain, or all pages.
step 2
Check the likely surface
Generation issues usually start with source text or AI provider state. Publishing issues usually start with route, cache, DNS, or certificate state.
- Try a smaller source text if generation fails.
- Verify DNS records if a custom domain is not active.
- Use the platform subdomain to separate site content from domain configuration.
step 3
Escalate with source-safe evidence
Support can diagnose faster from structured evidence that avoids credentials, private content, and raw provider logs.
- Share browser, route, timestamp, and redacted screenshot.
- Do not share passwords, tokens, API keys, or raw database connection strings.
- Mention whether a recent edit, upload, or DNS change happened before the issue.