409 Conflict — Causes & Fix
HTTP 409 (Conflict) means the request conflicts with the current state of the resource — for example, an edit that clashes with another change.
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 5–30 minutes
What it means
Causes include concurrent edits (someone else changed the record), duplicate creation, or a version/precondition mismatch. HTTP status 409 is defined in RFC 9110 (HTTP Semantics). This is a client-side (4xx) error — the request itself had a problem, so the fix is usually on the requester's side or in how the server validates the request.
Symptoms
- "409 Conflict" when saving or creating
- A record was modified by someone else
How to fix it
- 1
Reload and retry
1. As a user: refresh to get the latest version, then reapply your change.
- 2
Handle versioning (developers)
1. Use ETags/optimistic locking and surface a clear merge/retry path on conflict.
Frequently asked questions
Why do I get 409 when saving?
Something else changed the same record since you loaded it. Reload the latest version and reapply your edit.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.