| Previous | Next |
| HTTP_STATUS_MISDIRECTED_REQUEST | HTTP_STATUS_LOCKED |
HTTP_STATUS_UNPROCESSABLE_ENTITY
The request syntax and media type are acceptable, so the problem is usually semantic validation: an invalid field relationship, a domain rule violation, or a request that cannot be applied to the current resource.
Use the response details to correct the submitted data. A blind retry is not useful unless the client first changes the invalid instruction or the resource state.
Operational meaning of HTTP 422 for HTTP_STATUS_UNPROCESSABLE_ENTITY
HTTP 422 (HTTP_STATUS_UNPROCESSABLE_ENTITY) is a client-error response. AllStat records its meaning as “422 Unprocessable Entity”. For HTTP_STATUS_UNPROCESSABLE_ENTITY, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_UNPROCESSABLE_ENTITY
- Treat HTTP_STATUS_UNPROCESSABLE_ENTITY as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_UNPROCESSABLE_ENTITY, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_UNPROCESSABLE_ENTITY, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 422, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.