Where would I see a 424?

Inside a 207 Multi-Status body, or as the result of one step in a batch, next to the step that actually failed.

Should I retry a 424?

Not by itself. Resolve the dependency that failed and retry the whole batch.

HTTP 424 Failed Dependency

This operation failed because another operation it depended on failed first.

Defined in RFC 4918 §11.4 — 424 Failed Dependency · MDN reference

Where you meet HTTP 424 in production

WebDAV batch operations, and batch APIs that run steps in order: if step two fails, step three is reported as 424 rather than attempted.

Why you would test it

Appears inside batch and multi-status responses. Test that your client distinguishes the item that actually failed from the ones that failed because of it.

What your client should do about a 424

Find the root failure — usually a sibling result in the same response — and fix that. Retrying a 424 on its own changes nothing.

424 versus the codes it gets confused with

424 vs 207 Multi-Status — 207 is the envelope that carries several outcomes; 424 is one possible outcome inside it.
424 vs 409 Conflict — 409 is a conflict with this resource; 424 is a failure inherited from another.

Endpoints that return 424

1 endpoint in this playground answers with 424. Every one is free, needs no signup, and can be called from the browser or with curl.

GET https://funapi.dev/api/faults/v1/status/{code} — Returned on request (Fault Injection API) Open & run this endpoint

Questions about HTTP 424

Where would I see a 424?: Inside a 207 Multi-Status body, or as the result of one step in a batch, next to the step that actually failed.
Should I retry a 424?: Not by itself. Resolve the dependency that failed and retry the whole batch.

Other client error codes

All HTTP status codes · All 39 mock REST APIs · Getting started guide

Last updated 2 October 2026