job not found 🔌 API

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.

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 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.