HTTP 424 — Failed Dependency
HTTP 424
Failed Dependency
The request failed because another request it depended on failed first.
What 424 actually means
Nothing was wrong with this operation in itself — it simply could not be attempted because a prerequisite step did not succeed. In WebDAV that means one action inside an atomic batch failed, so the rest were abandoned. Outside WebDAV, some APIs use it when a downstream dependency they rely on returned an error, though 502 or 503 usually communicates that better.
Common causes
- One operation in a WebDAV batch failed, cancelling the others
- A dependent step in a multi-part transaction was rolled back
- An API reporting that a required upstream service failed
If you're just trying to view the page
- Look for the underlying failure — this error is a consequence, not a cause
- Retry the whole operation once the original problem is fixed
If it's your site
- Report the failing dependency, not just the dependent request; on its own a 424 tells the client nothing actionable
- For upstream service failures, prefer 502 or 503 — they are better understood and carry retry semantics
- In batch APIs, consider 207 with per-item results so partial success is visible
Reference
- Status code
- 424
- Reason phrase
- Failed Dependency
- Category
- 4xx — Client Error
- Defined in
- RFC 4918 §11.4
Common questions
- What does HTTP 424 mean?
- The request failed because another request it depended on failed first. Nothing was wrong with this operation in itself — it simply could not be attempted because a prerequisite step did not succeed. In WebDAV that means one action inside an atomic batch failed, so the rest were abandoned.
- How do I fix a 424 error?
- Look for the underlying failure — this error is a consequence, not a cause
- Is 424 a client error or a server error?
- 424 is in the 4xx range, which means client error. The request itself was the problem, so retrying it unchanged will usually return the same code.
Related pages
- 404 Not Found The server is reachable and working, but there is nothing at the address you ask
- 403 Forbidden The server understood the request and is refusing to allow it, and logging in wi
- 401 Unauthorized You need to authenticate, and either you did not or your credentials were reject
- 429 Too Many Requests You have sent more requests than the service allows in a given period.
- 400 Bad Request The server could not understand the request because something about it is malfor
- 413 Content Too Large The request body is bigger than the server is willing to accept.
- 422 Unprocessable Content The request is well-formed and understood, but the data in it fails the rules.
- 405 Method Not Allowed The URL exists, but it does not accept the HTTP method you used.
- 409 Conflict The request cannot be completed because it clashes with the current state of the
- 415 Unsupported Media Type The server will not accept the format of the body you sent.
- 408 Request Timeout The server gave up waiting for the client to finish sending its request.
- 410 Gone The resource was deliberately removed and is not coming back, and there is no fo