Every error.
A clearer next step.

No valid session or token was presented. Sign in and retry.

Both a session cookie and a bearer token were sent. Send exactly one.

The request did not carry an acceptable Origin. Browser calls must come from opensep.com itself.

The credential is valid but this account or principal type may not perform the action.

The action needs a recent sign-in. Sign in again and retry.

The human-verification token was missing, expired, or invalid.

A demo limit is spent: the grant’s one separation, today’s allowance, or the hourly burst cap. Sign up for a free account, or retry after the Retry-After interval when one is sent.

The account already has the maximum number of jobs queued or running (waiting jobs count). Finish or cancel one and retry.

The account is on hold (for example after a payment dispute). Contact support.

No such file for this account. Files are never visible across accounts.

The file passed its retention horizon and is gone. Uploads are deleted after 1 day. Results stay available for 3 days.

The declared size exceeds the upload limit for your plan. `detail` names the plan and the limit.

The audio is longer than the per-file limit for your plan. `detail` names the plan and the limit.

The upload was declared but the bytes never arrived, or the file is not ready yet.

The declared content type is not an audio or video type.

The file could not be decoded as audio, or its length could not be read from its header; `probe_error` on the file says which.

Too many declared uploads are still pending for this account.

The account holds as many uploaded bytes as its plan allows at once (10× the per-file limit); results do not count. Delete an upload or wait for one to expire; `detail` names the number. Uploads are deleted after 1 day. Results stay available for 3 days.

A job that is still running references this file.

No such job for this account.

The job is in a state where the requested transition is not allowed (for example cancelling a finished job).

The account has not accepted the current Terms and Privacy Policy. Open the app and accept them, then retry.

The job waited in the queue longer than the limit and was not started. Try again, or move to a plan with a faster queue.

RunPod kept the job in its own queue past the queue budget (one hour after submit), so it was cancelled there and never started. Nothing was charged; retry.

RunPod answered five status polls in a row that it had no such run, so the job was failed and its run cancelled there. Nothing was charged; retry.

This mutating request must carry an Idempotency-Key header.

The Idempotency-Key was reused with a different request body.

An identical request is still being processed. Retry after the Retry-After interval.

This Idempotency-Key's earlier attempt was refused or released its reservation, and nothing was created. Retry with a new Idempotency-Key; that is a fresh attempt.

The account has no active paid subscription for this action.

The payment provider did not respond correctly. Safe to retry.

The subscription is cancelling at the end of its period (resume it first, then change plan), or its period has already ended and the scheduled change is due.

The subscription has no scheduled plan change to withdraw; it already renews on its current plan.

The account already holds a live subscription (active or past due, cancelling or not). Checkout is refused before the payment provider is called, so a second subscription is never opened; manage or resume the existing one instead.

An operator approval was recorded against a gate the intent has since moved past. Re-read the intent and decide again.

Three revisions have already been recorded for this gate of this intent. Approve it or drop it instead.

The account is not frozen by a chargeback (it is not frozen, or frozen for another reason such as deletion), so the operator unfreeze has nothing to lift.

An operator lookup or a play of a customer file could not write its access record, so nothing was returned and no link was made. Safe to retry; the retry writes its own record.

Object storage did not answer twice. Nothing was stored; safe to retry.

The `Range` asks for bytes the file does not have; `Content-Range: bytes */<size>` gives its length.

The request body or query failed validation; `errors[]` lists the fields.

The feature is switched off right now; `feature` names which one.

Too many requests. Slow down and retry after Retry-After.

Request bodies must be application/json.

No such route or resource.

Something failed on our side. The `request_id` lets support find it.