Reference

Errors

API error codes, HTTP statuses, retry guidance and CLI exit codes.

API error codes

Code	HTTP	Meaning and fix
invalid_request	400	Malformed body or a parameter failed validation. The message names the field.
invalid_config	400	clockingcloud.yaml failed validation. Run `clockingcloud plan` locally to see every problem.
unauthenticated	401	Missing, invalid, expired or revoked API key.
insufficient_credits	402	Balance is zero or too low. Add credit in Billing.
forbidden	403	The credential is valid but may not do this.
not_found	404	No such instance, volume, run or key.
conflict	409	Name already exists, or the resource is in a state that blocks the action, such as starting a deleting instance.
quota_exceeded	422	You hit a limit on concurrent GPUs, volumes or keys. See Limits.
idempotency_conflict	409	The same `Idempotency-Key` was used with a different request body.
rate_limited	429	Too many requests. Honor `Retry-After`.
capacity_unavailable	503	No GPU of the requested type could be allocated in time. Retry.
internal	500	Unexpected error. Retry with backoff and include `request_id` if it persists.

Retry 429, 500, 502, 503 and 504 with exponential backoff and jitter. Always send an Idempotency-Key on POSTs you retry.
Do not retry 400, 401, 402, 403, 404, 409 or 422 without changing something first.

Exit code	Meaning
0	Success.
1	Unexpected error.
2	Invalid usage or invalid clockingcloud.yaml (API 400).
3	Not authenticated (API 401).
4	Insufficient credits (API 402).
5	Not found (API 404).
6	Conflict (API 409).
7	Timed out waiting.
130	Interrupted by Ctrl+C.

Something unclear or missing? Email hello@clockingcloud.com.