Reference
Error Meanings
What dashboard and API errors actually mean — and what to do next.
Branch on code, not wording. Messages static by design; infra strings never leak.
| Code | Means | Do |
|---|---|---|
400 INVALID_REQUEST | Bad input, tier, spec | Fix fields, don't retry same |
| 401 | Token missing/invalid | Re-login, refresh token |
402 INSUFFICIENT_BALANCE | Wallet short (requiredUsdCents vs availableUsdCents) | Top up, retry |
| 403 | No perm / quota / tier block | Check org caps, role. Retry won't help |
| 404 | Missing or hidden | Verify ID + workspace scope |
| 409 | State conflict (e.g. rollback while running) | Stop first, refresh state |
| 422 | Validation failed | Fix named fields |
| 429 | Rate limited | Back off, retry later |
500 INTERNAL_ERROR | Server side | Check status, retry safe ops only |
502 UPSTREAM_ERROR | Compute / payment upstream | Check upstream, retry per idempotency |
| 503 | Dependency unconfigured | Restore config, contact Support |
Snapshot/backup mutations return 202 = queued. Poll task ID, not done yet.
Full operator list lives in platform repo docs/reference/errors.md — this page is the customer subset.