424 🌐 HTTP

HTTP 424 Failed Dependency

The request failed because another action it depended on failed — part of a WebDAV multi-step operation or a batch.

Seen on: REST API

Meaning

424 comes from WebDAV (PROPPATCH, LOCK, MOVE of collections) and some batch APIs: one sub-operation failed, so the others in the same request were not applied. The real error is in the response body (often a 207 Multi-Status listing each item).

Common causes

  • One item in a batch/multi-status request failed
  • WebDAV operation on a collection where a child failed
  • Upstream dependency of a workflow failed

⚡ Quick fix

  1. Read the response body for the item that actually failed
  2. Fix that item and retry the whole batch
  3. Send items individually to isolate the failure

Detailed fix by platform

curl

  1. curl -i -X PROPPATCH https://dav.example.com/folder/ --data @props.xml # inspect the multistatus body

How to diagnose

  1. Body — Which sub-request failed and why?
  2. Batch — Does it work item by item?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.