HTTP 409 Conflict
The request conflicts with the current state of the target resource. The server cannot complete the request because it would create an inconsistency — such as a duplicate record or a version mismatch.
What does HTTP 409 mean?
The request conflicts with the current state of the target resource. The server cannot complete the request because it would create an inconsistency — such as a duplicate record or a version mismatch.
Common causes
- 1
Attempting to create a resource that already exists, e.g., registering a username or email that is already taken.
- 2
Optimistic concurrency conflict — two users edited the same record simultaneously and the second save conflicts with the first.
- 3
A state transition that is not allowed, e.g., trying to publish a document that is already published or cancelling an order that has already shipped.
How to fix it
- 1
Read the response body for details about the conflict. Most APIs explain which field or constraint was violated.
- 2
For concurrency conflicts, fetch the latest version of the resource, merge changes, and retry the request.
- 3
For duplicate-key conflicts, check if the resource already exists before creating it, or use an upsert operation if your API supports it.
Monitor for HTTP 409 errors
A sudden spike in 409 errors may indicate a race condition or broken deduplication logic in your application. Uptrack alerts you to status code changes so you can investigate before data integrity issues escalate.
Catch HTTP errors before your users do
Start free, or choose a plan, for 30-second monitoring and alert confirmation.
from $3/mo · 30-day money-back guarantee
Other HTTP status codes
- HTTP 408 Request Timeout
- HTTP 410 Gone
- HTTP 405 Method Not Allowed
- HTTP 413 Payload Too Large
- HTTP 404 Not Found
- HTTP 403 Forbidden
- HTTP 415 Unsupported Media Type
- HTTP 401 Unauthorized
- HTTP 400 Bad Request
- HTTP 422 Unprocessable Entity
- HTTP 429 Too Many Requests
- HTTP 451 Unavailable For Legal Reasons
- HTTP 500 Internal Server Error
- HTTP 502 Bad Gateway
- HTTP 503 Service Unavailable
- HTTP 504 Gateway Timeout
- HTTP 304 Not Modified
- HTTP 302 Found
- HTTP 301 Moved Permanently
- HTTP 520 Web Server Returns Unknown Error
- HTTP 522 Connection Timed Out
- HTTP 204 No Content
- HTTP 201 Created
- HTTP 200 OK