Skip to main content
Use code to identify a failure. Read param for the input to fix and details for the full context. See Errors for TypeScript and Python handlers.This catalog covers all 122 codes known to the SDK. A newer server can add codes; Meta lists the deployment’s vocabulary.
An API refusal raises an SDK exception. An accepted import can fail later and return a failure record instead. A skipped trial appears in skipped_trials. The job import section separates these cases.

Keys, credits, and quotas

Request inputs

Datasets and tasks

Dataset imports and packages

Resumable uploads

These codes apply to chunked dataset and job uploads. They describe the transfer, before an accepted import finishes processing.

Harness settings

Registered agents

Skills

Job secrets

These codes describe secret attachment during job creation. The managed-secrets client uses separate error handling.

Jobs and trials

Regrades

Analysis and task checks

Job imports

Job upload returns an import record before validation finishes. A later failure is returned as status: FAILED with failure.code, failure.message, and optional failure.details. Reading that record can succeed over HTTP.Job import failures can also use shared codes such as invalid_archive, dataset_not_found, dataset_version_not_found, no_active_version, and version_not_ready. Preserve an unfamiliar failure code: import failures can include values outside this API vocabulary, such as import_failed.

Filesystems and sessions

Organizations and invites

Temporary server capacity

These are capacity limits, separate from request rate limits. Each response provides details.max_concurrent, with no fixed retry delay. Retry after an in-flight operation finishes.

Server failures

unknown_error is an SDK fallback when a response provides no usable code. It is not one of the 122 codes above. Preserve the status, message, and request ID rather than guessing a cause.