HTTP 2xx
202 Accepted
The request was accepted for processing, but the processing has not finished. Common for async or queued work.
What causes it
- A job was queued rather than completed inline.
How to fix it
Expected for asynchronous processing. Poll or await a webhook for the final result.
Example response
A typical raw HTTP response a client receives for a 202, with the headers this code is defined around.
HTTP/1.1 202 Accepted
Content-Type: text/html; charset=utf-8Related codes
200Common
OKThe request succeeded. This is the normal response for a healthy page or API.201
CreatedThe request succeeded and a new resource was created as a result.204
No ContentThe request succeeded but there is no content to return.206
Partial ContentThe server is delivering only part of the resource, in response to a Range request.Know before your visitors do.
Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 2xx error, so you can fix it before it costs you.