Separate write intentions from transport attempts
Shows how to fix separate write intentions from transport attempts. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Assign one stable operation identity to the intended state change. If the intended payload changes, treat that as a new decision instead of silently reusing the previous identity.
Steps
- Assign one stable operation identity to the intended state change. Associate each HTTP attempt with its own request ID for diagnosis, while retaining the same operation key and payload for an identical retry. After an uncertain response, recover the committed resource before creating a new operation. If the intended payload changes, treat that as a new decision instead of silently reusing the previous identity.
When to use
You are seeing this: Associate each HTTP attempt with its own request ID for diagnosis, while retaining the same operation key and payload for an identical retry. Use this skill when you run into "Separate write intentions from transport attempts".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.