Studio

Troubleshooting

Common questions and problems, and what to do about them.

A build started but never finished

A first-time build takes about 2 to 4 minutes from the moment you send the prompt to the moment a live preview appears. Edits to an existing project are faster because the sandbox is already running.

If the build panel shows no progress after 5 minutes:

  1. Click Retry once. Transient errors - a network hiccup, a temporary capacity spike - clear on a fresh attempt.
  2. If it fails again, add a message describing what you wanted and start a new build. Studio uses your message as context for the next attempt.
  3. If repeated attempts do not succeed, use the in-app support button (the help icon in the top bar) to report it. Build diagnostics are attached automatically.
Note
When a build fails because of a problem on our side (not because you ran out of credits), the credits charged for that build are returned automatically. You will see the returned credits in your balance within a few seconds of the build ending.

The preview panel is stuck on "Starting your app"

The preview panel shows Starting your app while the sandbox boots and the project dependencies install. This is normal on a first build and typically resolves within a few minutes. You do not need to reload the page - the preview updates automatically.

If the panel stays on that message for more than 5 minutes after the build panel has marked the build as complete, try opening the project link in a new browser tab. If that does not help, contact support with your project link (the URL shown in the workspace browser bar).

Questions about credits and charges

See Credits explained for the full picture. The short version:

  • Every Build turn starts with a small entry hold of 10 credits. If the turn runs but writes no files (for example a plan-only or chat reply), the hold is returned and the turn costs nothing.
  • Turns that do change files are charged by actual usage. The final charge is shown in the build receipt.
  • Your balance may briefly show the 10-credit hold before it is settled against the real charge (or returned). This is not a double charge.
  • Free accounts receive 100 bonus credits on each day they run a build, up to 500 credits per UTC calendar month. These are in addition to the 500-credit monthly allowance and the one-time 1,000-credit signup grant.
  • Studio credits are not refundable (except for automatic system-fault refunds described above).

Data in published apps

By default, Studio generates apps that store data in the browser's local storage. This means:

  • Data a user enters is saved in their own browser and survives page reloads.
  • Data does not appear in a different browser or on a different device.
  • If a visitor opens the published URL on their phone, they will not see data entered on a desktop, and vice versa.

If you need data shared across all visitors (a real database, not browser storage), include that requirement in your prompt. For example: "Save submissions to a database so all visitors see the same data." Studio will generate an app with a backend connection instead.

Publish problems

To publish your app, click Publish after a build completes. The published URL uses the format <unique-id>.mudbase.app and is immediately shareable.

If you edit and republish but the live site looks unchanged, try a hard refresh in your browser (Ctrl+Shift+R on Windows and Linux, Cmd+Shift+R on Mac). If that does not update it, wait a minute and try again - CDN propagation can take a moment.

If the Publish button is not available, check that your most recent build completed successfully. The Publish button only appears after a clean build.

Note
The free plan allows up to 3 published sites on *.mudbase.app subdomains at the same time. If you have reached that limit, unpublish or delete a project before publishing a new one. See Limits and fair use for the full limits table.

Contact support

For persistent issues, use the in-app support button (the help icon in the top bar) or email support@mudbase.dev. Include your project link and a description of what you were doing when the problem occurred.

Chat with us