What Is a 424 Status Code?

The method could not be performed on the resource because the requested action depended on another action and that action failed.

For example, if a command in a PROPPATCH method fails, then, at minimum, the rest of the commands will also fail with 424 Failed Dependency.

• Source: RFC4918 Section 11.4

424 CODE REFERENCES

Rails HTTP Status Symbol failed_dependency

Symfony HTTP Status Constant Response::HTTP_FAILED_DEPENDENCY

Python HTTP Status Constant httplib.FAILED_DEPENDENCY

.NET HttpStatusCode.FailedDependency

Rust http::StatusCode::FAILED_DEPENDENCY

Go http.StatusFailedDependency

Python3.5+ http.HTTPStatus.FAILED_DEPENDENCY

Apache HttpComponents Core org.apache.hc.core5.http.HttpStatus.SC_FAILED_DEPENDENCY

Angular @angular/common/http/HttpStatusCode.FailedDependency

What causes a 424 status code?

A 424 status code occurs when the client makes a request to the server, but the request fails because it relies on a previous request that has failed.

This can happen for several reasons, including:

• Dependencies: If the request depends on another request that has not been completed successfully, the server may not be able to process the request and return a 424 status code.
• Timing issues: Sometimes, if the client sends multiple requests in quick succession and the server has not had time to process the previous requests, a 424 status code may be returned.
• Authentication issues: If the client is not properly authenticated, it may not be able to access the requested resource and receive a 424 status code.
• Server errors: If there is an error on the server side, such as a database connection error or an internal server error, the request may not be completed successfully, resulting in a 424 status code.
• Network issues: If there is an issue with the client’s network connection or the server’s network connection, it may not be able to complete the request, resulting in a 424 status code.

424 status code example

Here’s an example request and response for a 424 status code:

Request

GET /api/orders/123 HTTP/1.1
Host: example.com

Response

HTTP/1.1 424 Failed Dependency
Content-Type: application/json
Content-Length: 73

{
"error": "Failed Dependency",
"message": "The requested resource depends on another resource that has failed."
}

In this example, the client has made a request to retrieve information about an order with an ID of 123, but the server is unable to fulfill the request because it depends on another resource that has failed. The server returns a 424 Failed Dependency status code along with a JSON response body that provides more information about the error.

How to troubleshoot a 424 status code

If you receive a 424 status code, try these troubleshooting steps:

• Check the server logs: The server logs can give you a better understanding of what happened during the request. Look for any error messages or warnings that might indicate what went wrong.
• Verify the client request: Double-check that the client request is correct and complete. Make sure that all the required parameters and headers are present and correctly formatted.
• Check the server configuration: Verify that the server is properly configured and has all the required dependencies installed. Make sure that the server is up and running.
• Check for network issues: If the server is up and running, check for any network issues that might be preventing the client from communicating with the server. Look for issues with firewalls, proxies, or other network devices.
• Contact the server administrator: If you are unable to troubleshoot the issue on your own, contact the server administrator for assistance. They may be able to provide additional insights or help you resolve the issue.

Additional resources

• Learn about web development
• Learn about SEO
• Web development services from WebFX
• SEO services from WebFX
• MDN Web Docs
• W3Schools

Return to List of HTTP Status Codes