424 Failed Dependency
The method could not be performed because the requested action depended on another action which failed.
Usually happens because:
- ☑ WebDAV bulk transactions where a
🔍 Quick Checklist:
Meaning
The HTTP 424 Failed Dependency WebDAV status code indicates that the method could not be performed because the requested action depended on another action and that action failed (e.g. bulk operations where one item crashes).
Root Causes
- WebDAV bulk transactions where a sub-operation (like editing a folder parent) fails, causing child operations to be aborted.
| Cause | Frequency |
|---|---|
| WebDAV bulk transactions where a | ⭐⭐⭐⭐⭐ |
Common Mistakes
- Using 424 for general server crashes (use 500 or 503 instead).
How to Fix
Framework-Specific Examples
Returning 424 status for multi-step transaction failures in Express.
app.post('/api/steps', (req, res) => {
// if step 1 fails, return 424 for step 2
res.status(424).json({ error: 'Step 1 failed, aborting Step 2' });
});Server Configuration Examples
Nginx forwards status 424 downstream.
# Forwarded downstreamPrevention
- Design transactional APIs to rollback changes cleanly on sub-failures.
Frequently Asked Questions (FAQ)
Q: What is the origin of 424 Failed Dependency?
It was introduced in the WebDAV specification (RFC 4918) to manage parent-child resource constraints in directory tree commands.
Q: Can I use 424 in microservice architectures?
Yes. If an API gateway cannot process a request because a required internal microservice failed to reply or crashed, returning 424 is very semantic.
Q: Is 424 cacheable?
No. Failed dependency responses are never cached.
Q: How do clients handle 424 responses?
Clients should review which root dependency failed, address that issue (e.g. retry the first task), and re-submit the transaction.