| Previous | Next |
| HTTP_STATUS_REQUEST_TIMEOUT | HTTP_STATUS_GONE |
HTTP_STATUS_CONFLICT
The client might be able to resolve the conflict and resubmit. Common examples include concurrent edits, version mismatches, duplicate names, or state transitions that are no longer valid.
A useful 409 response identifies the conflicting field or current version. Use ETags or revision identifiers for optimistic concurrency instead of retrying the same stale update.
The response should explain the conflict well enough for the client to decide whether to refresh state, modify the request, or ask a user to resolve it. Typical examples include editing an outdated resource version or creating an object whose current state makes the requested transition impossible. Blind retries usually reproduce the same conflict.
Looking for a different code? Search another status or error code.