Error codes
Esta página aún no está disponible en tu idioma.
Every failure answers {"error":{"code":"<code>","message":"<English text>"}}. The code is one of the sixteen values below; the message is for humans and may change. The Studio shows both verbatim and adds a translated explanation.
invalid_request
Section titled “invalid_request”400. The request was malformed or a value was out of range: a name that does not match its pattern, a body that is not the expected JSON shape, a length over the limit. Field hints in the Studio and the limits list the rules.
authentication_required
Section titled “authentication_required”401. No valid bearer was presented, the session expired, the key was revoked — or a project key was used on an owner-only route (a valid credential on the wrong plane).
authorization_denied
Section titled “authorization_denied”403. The credential is valid but does not own this resource, for example a key naming a project other than its own via Host or X-Hyphae-Project — or, on an invite-gated deployment, a signup without a valid invite code (missing and unknown codes answer identically).
not_found
Section titled “not_found”404. Nothing with that id or name in this project — or a project key addressing another project, which is deliberately indistinguishable from “does not exist”.
conflict
Section titled “conflict”409. The resource already exists or is in a state that forbids the action (a bucket name taken, an account email in use).
payload_too_large
Section titled “payload_too_large”413. The body exceeds the route’s cap: 64 KiB on control-plane JSON, 8 MiB on /v2 bodies, CLOUDD_STORAGE_MAX_BYTES (32 MiB) on objects, 512 KiB on function source, 32 KiB on invoke bodies.
not_implemented
Section titled “not_implemented”501. The route exists in the contract but is not available in this build.
tenant_not_running
Section titled “tenant_not_running”503 on the data plane, 409 on head. The engine process is not running, so there is nothing to forward to. Wake the project up first.
tenant_running
Section titled “tenant_running”409. The engine holds the data directory lock while running, and snapshots/restores need it. Put the project to sleep, retry, wake it up again.
function_runtime_missing
Section titled “function_runtime_missing”501. No node or deno runtime on the Cloud host. Deploys are stored; invokes cannot run.
function_timeout
Section titled “function_timeout”504. The function did not answer within CLOUDD_FN_TIMEOUT_MS (5 s); its process group was killed.
function_bad_output
Section titled “function_bad_output”502. The function exited non-zero or printed something other than one JSON object with status and body. Its stderr is included in the message.
function_busy
Section titled “function_busy”429. Two invocations of this project are already running. Retry shortly.
orchestrator_unavailable
Section titled “orchestrator_unavailable”503. The daemon could not find or run the pinned Native binary. An operator must fix the host; GET /readyz also reports it.
upstream_unavailable
Section titled “upstream_unavailable”502/503. The engine did not answer within 30 s or the blob backend is unreachable.
internal
Section titled “internal”500. Something failed inside the daemon. The request id is in the server logs.