job_limit_reached (2004, HTTP 409) · TranscriptFetch API error

The account already runs as many channel jobs as its plan allows. Wait for one to finish (or cancel one), then start the next. error.details carries the cap (max) and how many are running (current).

Number2004

HTTP status409Conflict

Familyaccount2xxx · your account or plan

Example response

JSON

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "job_limit_reached",
    "number": 2004,
    "message": "The account already runs as many channel jobs as its plan allows. Wait for one to finish (or cancel one), then start the next. error.details carries the cap (max) and how many are running (current).",
    "docs": "https://transcriptfetch.com/docs/errors/job_limit_reached",
    "details": {
      "max": 1,
      "current": 1
    }
  }
}

Every failure carries error.code, error.number, error.message and error.docs, plus at most one of retry_with (the request change that would succeed), details (structured specifics) or issues (validation problems).

What it means

The account already runs as many channel jobs as its plan allows. Wait for one to finish (or cancel one), then start the next. error.details carries the cap (max) and how many are running (current).

Why it happens

The account already runs as many channel jobs as its plan allows at once: 1 on Free, Basic and Pro, 2 on Mega and Scale. A job counts while it is queued or running. error.details carries max and current.

What to do

Wait for a running job to finish (GET /api/v2/jobs/channel/{jobId} shows its progress), or cancel one with DELETE /api/v2/jobs/channel/{jobId}.

Retryable? Yes, once a job has finished or been cancelled. Nothing was created or charged. Every error response carries a request_id; include it when contacting support.