202 Accepted

The request was accepted for processing, but processing has not completed — the async success code. The server is promising nothing beyond 'I have queued it'; the actual outcome arrives later via polling, webhook, or a status URL.

What usually causes it

  • Async job submission (report generation, batch imports, video processing)
  • Queue-backed write paths that acknowledge before durability

How to debug and fix it

  1. A 202 with no way to learn the outcome is an API design bug — return a status URL (Location or body) or emit a webhook.
  2. Client-side: never treat 202 as 'done'; poll the status endpoint with backoff.
  3. If the job silently disappears after a 202, inspect the queue between the API and the worker — the request likely died there.

Easily confused with

Debugging an API? Build and inspect requests, check response headers, or read the full status-code debugging guide.