Troubleshooting
Common messages you might see in the console, what they mean, and how to resolve them.
Most problems in the console show up as a plain-language toast or banner. Here's what the common ones mean.
Common messages
| Message | What it means | What to do |
|---|---|---|
| "Already exists" | You're trying to create something with a name that's already taken in this project or workspace. | Pick a different name, or open the existing one instead. |
| "Not permitted" | Your role on this project or team doesn't allow this action. | Ask an Owner or Admin to perform it, or to change your role — see Members & roles. |
| "Insufficient credits" | Your credit balance is too low to start this job or instance. | Top up your balance — see credits. |
| "Too many attempts, please wait" | You've triggered the same action too many times in a short window. | Wait a minute and try again — this resolves itself, no action needed beyond that. |
| "Something went wrong" | An unexpected error on our side. | Retry the action. If it keeps happening, reach out to support with the approximate time it occurred. |
If a deployment fails
Open the failed deployment's build logs first — most failures are a missing build step, a wrong start command, or a missing environment variable, and the log usually names exactly which one. See Logs & rollbacks.
If a resource seems stuck
A project, database, or instance can sit in a provisioning or transitional status for longer than expected during heavy load. Give it a few minutes and refresh the page before assuming something is wrong — if the status still hasn't moved after a reasonable wait, that's worth a support ticket rather than repeatedly retrying the same action.
Note
Still stuck? Support contact details and status updates are available from Account → Support in the console.