Workspace Start Errors, Capacity, and Credits
How workspace launch failures are presented to users, what busy-controller and concurrency states mean, and when AI-credit balance blocks a launch.
Workspace Start Errors, Capacity, and Credits
Where you see this in the app
This page documents the launch-error panel shown in the workspace section when Open AI workspace or Open interactive preview fails.
The error area can include actions such as:
Add creditsRetryClose all active workspaces
Controllers busy vs concurrency limit vs credits
Not all launch failures mean the same thing.
The main user-facing cases are:
| State | What it means |
|---|---|
Workspace credits required | The billed wallet does not currently cover the launch cost |
Workspace controllers are busy | No controller capacity is available right now, so retry later |
Workspace unavailable with a concurrency limit message | Too many active workspaces are already open for the current user |
The app intentionally separates capacity problems from wallet problems because the next step is different for each one.
Add credits, Retry, and Close all active workspaces
These buttons are not interchangeable.
| Action | Best use |
|---|---|
Add credits | Use when the wallet is the blocker |
Retry | Use after a temporary controller-capacity problem or after fixing another issue |
Close all active workspaces | Use when your own active-session limit is the blocker |
If the app offers Close all active workspaces, that usually means the current problem is not global capacity but your own current concurrency limit.
How author vs viewer errors differ
Authors and viewers do not always see the same language.
For wallet problems:
- the author is told that the workspace is billed to the author's AI credit wallet,
- a viewer may instead see that the workspace is temporarily unavailable because the post author needs to top up credits.
That distinction matters because a viewer often cannot directly fix the wallet state.
What to try first
Use this order:
- If the panel offers
Add credits, check the wallet first. - If the panel offers
Close all active workspaces, close older sessions and try again. - If the message says controllers are busy, wait briefly and retry.
- If the same error persists, treat it as a runtime availability problem rather than a prompt/content problem.
Related docs
Related docs
See it in action
Previous
Workspace Close-All Cleanup and Partial Failures
How the Close all active workspaces action behaves, what full vs partial cleanup results mean, and how retry-after-cleanup works when a launch was blocked by concurrency limits.
Next
Workspace Defaults, Env Vars, and Runtime Commands
How the Defaults tab controls live preview startup, static preview and published-site paths, JSON env/secrets, and who can open or edit a workspace.