Common messages and what to do

"You do not have permission to perform this action."

Your role doesn't include this action. Ask a workspace administrator or owner to change your roles in Settings › Members; see members and roles. Some decisions are human-only, so an agent gets This decision requires a human reviewer.

"Write access for this workspace is suspended. Read and export remain available."

The workspace can't be changed right now, usually because of a billing problem. Everything stays readable and exportable; an owner or billing operator can fix it in Billing & usage.

"This needs N usage units but M remain…"

You've reached your plan's usage allowance for this month. On Explore, new runs stop until next month or an upgrade. On paid plans, check whether overage is set up and whether the spend cap was reached; an owner can raise the cap in Billing. Work that was already running finishes. See plans and seats.

"This needs about N credits and M are available."

Generation needs more credits than you have. Buy a credit pack in Billing, or wait for the daily cap to reset if it says the daily limit was reached. See usage units and credits.

"All N editor seats are in use…"

Every editor seat is taken. Add an editor seat in Billing, or invite the person as a reviewer: reviewers are free.

"Your plan includes N projects…"

You've reached your plan's project limit. Archive a project you no longer need, or upgrade.

"Agent connections (MCP) are included from the Studio plan…"

Connecting a coding agent needs the Studio and Team plan.

"Implementation runs on your own repositories need the Studio or Team plan."

Builds on your own repositories need a paid plan; the sample repository works on every plan.

"Too many attempts. Wait a few minutes and try again."

Rate limits protect sign-in, agent requests and connections. Wait a minute or two and try again.

"… isn't set up yet" or "… isn't available here yet"

The feature depends on a provider or sandbox that this deployment doesn't have configured, such as image generation, live previews, component pictures from code or Figma import. The notice says what still works, and Technical details (collapsed) names the missing piece for whoever administers the deployment.

"You can't approve your own release."

Your workspace's approval policy asks someone other than the person who sent the release to approve it. Ask a teammate to review it, or ask an administrator to look at Settings › Review & approval. See approval policies and team review.

Ship says a release isn't approved

Ship checks a release against the approval policy it was sent with. Open the release in Review to see what is still missing: an approval, a decision on a screen, an open request for changes or an open comment.

"Pictures of v… can't be taken on this server."

Release pictures need a headless browser on the server that draws them, and this deployment doesn't have one. The live previews in Review still work. See compare release pictures.

Your coding agent gets outside_tool_profile or release_not_approved

outside_tool_profile means the tool isn't in the connection's tool profile: connections from Connect your agent and OAuth use the 13 implementer tools. Create a token with the full set in Settings › Agent access if your agent needs more. release_not_approved means there is no approved release to build from or link to yet. See the MCP server.

Contacting support about an error

Error responses carry a correlation ID. If you can see one (for example in Technical details), include it when you send feedback or contact support, so the problem can be traced without sharing your data.