Studio
Build failures and capacity
Most Studio builds complete without issue. When something goes wrong, this page explains what the messages mean and what to do next.
Build failed
A "Build failed" message usually means a dependency conflict or a TypeScript error in the generated code. Studio runs auto-fixes for common errors at no charge. If the build still fails after automatic recovery:
- Click Retry once without changing anything - transient errors clear on a fresh attempt.
- If it fails again, add a chat message describing the specific error you see in the terminal panel. Studio uses that context for the next attempt.
- If a build stalls for more than five minutes with no progress, use the in-app support button (the help icon in the top bar) to report it. Diagnostics are attached automatically.
At capacity
"At capacity" means too many builds are queued across the platform right now. Your project and all its files are safe. The queue is self-clearing: capacity is usually available again within a few minutes. No action is needed - try starting a new build once the message clears.
Out of credits
When your credit balance reaches zero, new builds are blocked. Your project, its files, and any published sites are not affected. To continue building, upgrade your plan or wait for your next daily or monthly credit grant.
Build produces no files or is missing screens
Occasionally a build completes but produces fewer files than expected. This is usually a recoverable state: describe the missing screens in a follow-up chat message and trigger another build. If re-building does not resolve it, report it via the support dialog with the build ID shown in the terminal panel.
Contact support
For persistent failures, use the in-app support dialog (help icon in the top bar) or email support@mudbase.dev. Include the project ID (visible in the workspace URL) and a description of what you were building when the failure occurred.