Troubleshooting
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 fails before source delivery, Mythos leaves the last working source version in place. First distinguish a failure from a request that is paused for your answer, a connection, or approval. Complete the requested step when you want Mythos to continue.
Include the exact visible message when you ask for help. Do not paste passwords, access tokens, or private keys.
Continue a Build paused at its credit limit
Read the budget card and the work completed so far. Raise the limit to continue the same saved Build when you want more work, or stop it. A paused Build is not a reason to send the original request again. See Credits and usage.
Check a connected service
A saved credential, permission to use a provider resource, and a project’s link to that connection are separate checks. Open More → Connectors, confirm that the intended connection is linked, and follow any reconnect or setup message. See Connect your tools.
Check an uncertain result
A slow response does not always mean an action failed. If a code save or restore is being verified, use Check save status or Check restore status before sending the same operation again.
For a connected-service action with an uncertain result, inspect the service for the record, message, or other effect first. Repeating it without checking can create a duplicate. Include the uncertain status when you contact support.
Reload a blank preview
A preview can remain blank while it is starting or if the current page cannot render.
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. Check its backend and access rules as well as the page.
Check the expected behavior
Confirm what should be saved, who owns the record, and what should happen after submission. Include the exact error or the point where the data disappears.
Check the backend connection
Open the project’s Cloud view and review the managed backend. If the connection needs attention, resolve it through the workspace’s Supabase connector.
See Managed Supabase, including row-level security and storage policies. Keep database passwords, secret keys, and private API credentials out of prompts and browser code.
Publish the latest version
Changes in the workspace update the preview first. They do not replace the public version until you publish again.
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, email support@mythos.new. Include:
- your account email;
- 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.