Help
Troubleshooting
Recover from a failed build, blank preview, form that does not save, or published site that still shows an older version.
Start with what you can see. Keep the project open, note the last action you took, and follow the matching recovery path below.
Retry a failed build
If a build ends with a failure message, Mythos leaves the last working version in place.
Read the final message
Look for a specific file, connection, or request that needs attention.
Reduce the request
Ask for one clear outcome instead of repeating a large multi-part request.
Try once more
Send the focused request. If the same failure repeats, stop retrying and contact support.
Include the exact visible message when you ask for help. Do not paste passwords, access tokens, or private keys.
Reload a blank preview
A preview can remain blank while it is starting or if the current page cannot render.
Wait for the build to finish
Do not refresh while the activity card still shows work in progress.
Reload the preview
Refresh the preview once the result card appears.
Open the result again
Use the latest result card to reopen the current preview.
Describe the blank state
If it remains blank, send a focused edit that names the route and what should appear there.
If the preview repeatedly fails to open across projects, contact support rather than changing the project to work around it.
Understand a form that does not save
A visual form is not persistent by itself. New application-backend connections are currently unavailable in the workspace, and the former More → Cloud flow has been retired.
Check the expected behavior
Confirm whether the form only changes the page or actually sends data to a backend already present in the project source.
Keep secrets out of the browser
Do not paste a database password, service-role key, or private API key into a prompt or Vite environment variable.
Choose a safe next step
Continue with frontend behavior, manage an existing backend outside the retired Mythos flow, or wait for the managed Mythos backend.
See Supabase connection status for the current backend availability and legacy-resource policy.
Publish the latest version
Changes in the workspace update the preview first. They do not replace the public version until you publish again.
Check the preview
Confirm the latest copy, layout, links, and forms.
Publish again
Open the publish flow and publish the current version.
Open the public URL
Reload the live page and verify the changed area.
Publishing changes what visitors see. Review the current preview before you continue.
Correct a result that drifted
If several edits moved the project away from the intended direction, open History and restore the last version that worked. Then make one focused correction. See Fixing a result that isn't right for examples.
Contact support
If the same problem continues, use the in-app support form, email support@mythos.new, or message
@mythos_support. Include:
- the project URL or project ID;
- what you tried to do;
- what you expected;
- the exact message or visible result;
- whether the issue repeats after a refresh.