> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mythos.new/reference/troubleshooting/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server.

# 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 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.

#### 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.

## 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](/introduction/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](/integrations/introduction).

## 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.

#### 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. 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.

#### Ask for a focused diagnosis

Ask Mythos to inspect the form's save action and the relevant database or storage access rule.
Do not disable access controls merely to make an error disappear.

#### Test the complete flow

Submit a test record, reload, and confirm it remains available to the intended user.
Check that a different user cannot read private data.

See [Managed Supabase](/integrations/supabase), including
[row-level security](/integrations/supabase#row-level-security) and
[storage policies](/integrations/supabase#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.

#### 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.

> **Warning**
>
> 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](/prompting/debugging) for examples.

## Contact support

If the same problem continues, email [support@mythos.new](mailto: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.

## Related

* [Support](/reference/support-policy)
* [Writing good prompts](/prompting/writing-good-prompts)
* [Publish your site](/publishing/publish)

> Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.