202 Accepted
2xx success
The server accepted the request for processing but has not completed it, so the eventual outcome is not yet known to the client.
Common causes
- Work is queued behind a worker or job runner.
- An async import started and the result will arrive later.
- A webhook or batch endpoint defers processing to a background task.
How to fix it
- Return a status or polling URL so the client can track completion.
- Document the expected processing time and a final-state contract.
- Alert on jobs that never leave the queue so the 202 does not become permanent.
What it means for redirects and SEO
Accepted work may finish after the response, so a link checker sees 202 and stops. Pages rendered asynchronously behind a 202 can be indexed thin or empty. Do not submit polling endpoints for indexing.