## TL;DR

If the key conflicts with a different payload, stop and inspect the intended change.

## Steps

1. Assign an operation key before sending the write and retain the exact payload.
2. When the response is lost, treat the outcome as unknown. Do not create a new operation automatically.
3. Retry the identical payload with the retained key when the endpoint supports it.
4. Read the returned resource ID through its normal detail endpoint.
5. Confirm its intended fields and attribution.
6. If the key conflicts with a different payload, stop and inspect the intended change.
7. Present success only after the committed result is known.

2. Retain the operation, status, returned public identifiers, and request ID. Distinguish a confirmed result from an assumption.

## When to use

You are seeing this: Assign an operation key before sending the write and retain the exact payload. Use this skill when you run into "Recover an uncertain write without creating a duplicate".

## 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.
