Failed Dependency
The method could not be performed on the resource because the requested action depended on another action and that action failed.
What it means
The HTTP 424 Failed Dependency client error response code means that the method could not be performed on the resource because the requested action depended on another action and that action failed.
This is primarily used with the WebDAV `207 Multi-Status` code to indicate that an operation within a PROPPATCH batch failed because a prerequisite operation in the same batch failed.
How it works
- 1The client sends a batch request with Operation A and Operation B.
- 2Operation B explicitly depends on Operation A succeeding.
- 3Operation A fails.
- 4The server aborts Operation B and returns 424 for it.
Why you're seeing this
- • A previous operation in a batch sequence failed.
How to fix it
- • Fix the root cause of the initial failure before retrying the dependent operations.
Framework Implementations
Express.js
app.post('/batch', (req, res) => {
// In custom batch APIs, returning 424 for skipped operations is valid.
res.status(207).json({
op1: { status: 400 },
op2: { status: 424 }
});
});Real-Life Scenarios
Used in batch API requests (or WebDAV) where transactional dependencies exist between items.
Batch Processing
A request attempts to 1. Create a Folder and 2. Move a File into that Folder. If Step 1 fails, Step 2 returns 424 because its dependency (the folder) was not created.
HTTP Transaction
1. Client Request
PROPPATCH /docs HTTP/1.1
2. Server Response
HTTP/1.1 424 Failed Dependency
SEO Implications
None.