409 Conflict
4xx client error
The request conflicts with the current state of the resource, such as two editors writing the same version or a duplicate unique key.
Common causes
- Concurrent writes to the same record with stale versions.
- An insert collides with an existing unique constraint.
- Two batch jobs act on overlapping resources.
How to fix it
- Return the conflicting state or field so the client can reconcile.
- Require If-Match or a version token on updates.
- Serialize writes per record with a lock or queue.
What it means for redirects and SEO
Conflict on writes, not reads, so crawling is rarely affected. Concurrent edit flows and unique-key clashes cause it. Resolve it in the application rather than with a redirect.