> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythos.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fixes for common Mythos issues — a failed-and-refunded build, a blank preview, a form that won't save, stale published content, and running out of credits.

Most problems in Mythos fall into a handful of patterns. This page lists each one with what you see
and what to do. If a build failed, the first thing to know is that **you were not charged** — every
generation ends in either a delivered result or a full refund, never a silent loss of credits.

<Note>**Cost reminder:** a new project costs **3 credits**, an edit costs **2**, a template remix
costs **5**. A build that fails is **refunded in full** automatically — re-prompting after a failure
costs nothing extra. See [Credits & pricing](/introduction/credits-and-usage).</Note>

## Common issues

<AccordionGroup>
  <Accordion title="My build failed — was I charged?">
    No. Every generation ends in exactly one of two states: a delivered, verified result, or a clean
    message plus a **guaranteed refund**. If a build did not deliver, the credits go back to your
    balance automatically — you are never charged for a result you did not get.

    **What to do:** read the message, then **re-prompt**. A failure is usually transient, so sending
    the same prompt again often works. If it keeps failing, try making the prompt more specific or
    breaking a large request into smaller steps.

    | Outcome   | What you see                                     | Your credits                          |
    | --------- | ------------------------------------------------ | ------------------------------------- |
    | Delivered | A result card with a preview                     | Spent (3 build / 2 edit / 5 remix)    |
    | Refunded  | A short, plain message that something went wrong | **Refunded in full** — re-prompt free |

    <Tip>If your prompt asked for a lot at once, a smaller, clearer prompt is more likely to deliver in
    one build. See [Writing good prompts](/prompting/writing-good-prompts).</Tip>
  </Accordion>

  <Accordion title="The preview is blank">
    A blank or white preview usually means the live preview is still starting up, or the page hit an
    error while loading.

    **What to do:**

    1. Give it a few seconds — the preview spins up after a build finishes.
    2. Refresh the preview.
    3. Open the preview again from the result card.
    4. If it is still blank, send an edit describing what you expected to see (for example,
       "the page is blank — show the landing section"). The agent can rebuild the part that failed.
  </Accordion>

  <Accordion title="My form doesn't save anything">
    Apps Mythos builds are **frontend-only by default**. A form will look and behave correctly, but it
    has no database to save into until you connect one. Mythos uses **bring-your-own Supabase**: you
    connect your own Supabase project, and the agent wires the form up to it.

    **What to do:** connect a Supabase project in **Services → Cloud**, then ask the agent to save the
    form's data. For example:

    ```text theme={null}
    Connect this contact form to my Supabase project and store each submission in a "messages" table.
    ```

    <Note>Until you connect a Supabase project, forms are simulated on the frontend only — they do not
    persist data. The connection is your own Supabase, not a Mythos-hosted database.</Note>
  </Accordion>

  <Accordion title="My published site shows old content">
    Publishing produces a **production build** of your site and serves it as static files. A change you
    made in the workspace after publishing does not appear on the live URL until you **publish again** —
    editing the project updates the preview, not the published site.

    **What to do:** make your edits, confirm them in the preview, then re-publish so the live URL picks
    up the new build.

    <Warning>A published site is public on the internet. Re-publishing replaces what visitors see — make
    sure the change is what you want live before you publish.</Warning>
  </Accordion>

  <Accordion title="I ran out of credits">
    A new project costs 3 credits, an edit costs 2, and a template remix costs 5. When your balance is
    too low for the next action, the build will not start.

    **What to do:** buy more credits. Open **Pricing** from your dashboard or the credits menu and pick
    a pack:

    | Pack                     | Credits | Price | Per credit |
    | ------------------------ | ------- | ----- | ---------- |
    | **Pro** *(most popular)* | 100     | \$30  | \$0.30     |
    | **Ultra**                | 1,000   | \$270 | \$0.27     |

    Both packs are paid once in **USDT on the TRON network (TRC-20)**, and **credits never expire**. New
    accounts also start with **5 free credits**. See [Credits & pricing](/introduction/credits-and-usage).

    <Note>Unused credits can be refunded in **USDT within 30 days of purchase** — reach out on Telegram
    [@mythos\_support](https://t.me/mythos_support).</Note>

    <Tip>Plan mode is free — answering questions and reviewing a plan costs nothing, so you can shape a
    project without spending credits until the build runs. See [Plan mode](/features/plan-mode).</Tip>
  </Accordion>
</AccordionGroup>

## Still stuck?

If none of the above fixes it, reach support on any of three channels: email `support@mythos.new`,
Telegram [@mythos\_support](https://t.me/mythos_support), or the in-app support form on the **Help**
page. All three land in the same queue and we reply within one business day. When reporting a bug,
include what happened, what you expected, and any project IDs or URLs. See
[Support policy](/reference/support-policy) for what is covered.

## Related

* [Credits & pricing](/introduction/credits-and-usage) — costs, refunds, and buying more credits.
* [Support policy](/reference/support-policy) — what support covers and how to reach it.
* [Plan mode](/features/plan-mode) — shape a project for free before spending credits.
* [Writing good prompts](/prompting/writing-good-prompts) — fewer failed builds, fewer edits.
