job not found API Origin: Application & API OSI layer 7 · Application Last updated 13 Oct 2026

API Error: Job / operation not found or expired (async task ID unknown)

The status URL or job ID for an asynchronous operation (export, import, render, batch) doesn’t exist any more, or never existed.

Exact message you may see job not foundoperation not foundJob does not existtask not foundexport not found
Seen on: REST API

Meaning

Long-running APIs return a job/operation ID and let you poll it. Results are kept only for a retention window (hours to days); polling after that, polling the wrong region/endpoint, or using an ID from a failed submit returns 404 “job not found” or “operation not found”.

Common causes

  • Polling after the provider’s retention window
  • Job ID from a submit that actually failed
  • Wrong region/endpoint or account for the job
  • ID truncated or mixed up between jobs

⚡ Quick fix

  1. Store the job ID with the submit response and check the submit succeeded
  2. Poll within the retention window, or use the provider’s completion webhook
  3. Resubmit the job if it expired

Detailed fix by platform

Node.js

  1. javascript
    const { id } = await api.exports.create(params);      // persist id + created_at
    let job; do { await sleep(5000); job = await api.exports.get(id); } while (job.status === 'running');

How to diagnose

  1. Submit — Did the create call succeed and return this ID?
  2. Age — Time since submission vs retention policy
  3. Scope — Same account/region/endpoint?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

12 UNIMPLEMENTED — gRPC Error: 12 UNIMPLEMENTED: unknown service x / Method not found (API)12 UNIMPLEMENTED404 — HTTP 404 Not Found (HTTP)404BadDigest — Upload error: checksum mismatch (BadDigest / Content-MD5 did not match / XAmzContentSHA256Mismatch) (API)BadDigestCannot return null for non-nullable field — GraphQL: Cannot return null for non-nullable field Query.user (API)Cannot return null fo…concurrent_requests_limit — API Error: Too many concurrent requests (concurrency limit reached) (API)concurrent_requests_l…CORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSECONNRESET — Error: socket hang up / read ECONNRESET (API)ECONNRESETENOTFOUND — Error: getaddrinfo ENOTFOUND host / Name or service not known (API)ENOTFOUNDjob not f…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.