Why ETag Conflicts Cause 412 Precondition Failed
Debug optimistic concurrency failures where stale ETags, If-Match headers and cached resource versions cause rejected API updates.
Quick Answer
ETag conflicts cause 412 Precondition Failed when a client updates a resource using an old version token. The server compares If-Match with the current ETag and rejects the write to prevent overwriting newer changes.
Example Scenario
Two users edit the same settings page. User A saves first. User B saves later from a stale tab and receives 412. The request body looks valid, but the If-Match header identifies an older resource version.
Step-by-Step Explanation
- Read the current ETag when fetching the resource.
- Send If-Match on updates that require concurrency protection.
- Compare request ETag with current server version.
- Refetch after 412 before retrying.
- Show conflict UI instead of blind overwrite.
- Avoid caching stale ETags across accounts or resources.
Start by Naming the Contract That Broke
ETag conflicts cause 412 when clients try to write with stale resource versions. Debugging is slower when every symptom is treated as a generic API failure. Name the contract first: request shape, response shape, retry behavior, file type, time zone, numeric precision, logging policy or delivery semantics. Once the contract is named, each observation has a place to belong.
The most useful first signal is usually a 412 response after an otherwise valid update. It tells you which boundary produced the failure and prevents the team from rewriting unrelated client code. Keep the original request, response or log line available while you investigate.
A good working note should say what was expected, what actually happened and which layer observed it. That note is more valuable than a screenshot of a stack trace because it can be compared with documentation, tests and production logs.
If the issue is intermittent, keep one failing sample and one passing sample from the same release window. The passing sample prevents overfitting the fix to one user, while the failing sample keeps the investigation grounded in evidence instead of guesses about the system.
Separate Symptoms from Evidence
The visible symptom may be If-Match header differs from current resource ETag, but the evidence should be more precise. Capture the GET response ETag and later update If-Match header, then compare it with a successful case from the same environment. Environment, user role and feature flag differences can otherwise look like code regressions.
Avoid starting with broad fixes. First check server-side current resource version. If that detail differs from the healthy request, you have a concrete lead. If it matches, move to the next layer instead of guessing.
When multiple teams are involved, preserve the raw evidence in a safe form. Redact secrets, but keep field names, status codes, headers, timestamps and request ids. Sanitized evidence still lets another team reproduce the reasoning.
Look for Boundary Translation Errors
Many production bugs happen when data crosses a boundary and changes meaning. A browser form, generated client, proxy, queue worker, database mapper or logging pipeline can transform the value before the final system sees it.
For this issue, inspect the timing of competing edits or cached reads. That is where small differences usually become visible. A value may still look reasonable to a human while failing the receiver's stricter expectation.
Use comparison tools when the payload is large. Diff the failing sample against a known-good sample, then reduce it to the smallest input that still fails. A minimal failing sample turns a vague incident into a contract discussion.
Boundary errors also need ownership clarity. Decide which component is allowed to transform the value and which component must reject it. Without that decision, every layer may add a small compatibility patch, and the system becomes harder to reason about after the incident.
Choose a Fix That Matches the Failure Mode
The first safe fix is often refetching and merging after a 412 conflict. It addresses the observed boundary instead of hiding the symptom. If the problem is a contract mismatch, the fix should update the producer, consumer or documented contract deliberately.
The second fix to consider is clearing stale cached versions when switching resources. This is useful when old clients, partner integrations or delayed deployments mean two shapes must be accepted for a short time. Compatibility should be explicit and temporary where possible.
A third option is returning a conflict response that includes safe current metadata. Use this when the system needs better operational visibility before making a behavioral change. Good diagnostics can prevent a small correction from becoming a larger regression.
Keep Production Diagnostics Safe
Diagnostics should explain the failure without exposing sensitive data. For this topic, useful logs include request id, status code, safe field paths, environment and a short reason code. They should not include tokens, full personal records or secret payloads.
If the failure reaches support, include resource id, request ETag and current ETag logged together. That gives the next debugger a trail without requiring access to private customer data. It also helps separate one-off bad input from a systemic contract drift.
When adding logs, add deletion and retention awareness. Debug logs that are safe today can become risky if they accumulate raw payloads for months. Prefer structured fields over copied bodies.
A safe diagnostic should also be cheap to leave in place. If it requires developers to enable raw payload logging during every incident, the next emergency will recreate the same privacy and security risk. Prefer stable reason codes, counters and compact metadata that can remain active in production.
Prevention Checklist
Add a regression test for two-tab edit and stale cache update cases. The test should fail when the boundary behavior changes unexpectedly. A small test around the contract is often more valuable than a broad snapshot that nobody reviews.
Review ETag forwarding and cache behavior during release during release. Many bugs in this category appear during rolling deploys, integration updates or data migrations, not during a clean local run.
Document which writes require If-Match and which allow overwrite. The goal is not a long policy page; it is a short, accurate rule that future developers can apply while changing the same path.
After the fix, replay the original failing case and one known-good case. If both behave correctly, record the evidence in the incident or changelog. This closes the loop and keeps the next investigation from starting over.
Code Examples
await fetch('/api/settings', {
method: 'PUT',
headers: { 'If-Match': etag, 'Content-Type': 'application/json' },
body: JSON.stringify(settings)
});if (response.status === 412) {
const latest = await fetch('/api/settings').then(r => r.json());
showConflict(latest);
}console.log({ requestId, resourceId, ifMatch, currentEtag, status: 412 });Common Mistakes
- Retrying 412 without refetching current state.
- Treating ETag as a cache detail only.
- Sharing ETags between different resources.
- Using stale tabs to overwrite newer changes.
- Hiding conflict details behind a generic save failed message.
FAQ
What does 412 mean?
A precondition such as If-Match failed, commonly because the resource changed.
Should the client retry automatically?
Not blindly. It should refetch and resolve the conflict.
Is ETag only for caching?
No. It is also commonly used for optimistic concurrency.
What should users see?
A conflict message with a way to review or merge current data.