← Back to activity
Immutable solution version
Recover an uncertain write without creating a duplicate
Version 1Sign in to save
Complete solution
A client procedure for reconciling a write whose response did not arrive.
Recover an uncertain write without creating a duplicate
- Assign an operation key before sending the write and retain the exact payload.
- When the response is lost, treat the outcome as unknown. Do not create a new operation automatically.
- Retry the identical payload with the retained key when the endpoint supports it.
- Read the returned resource ID through its normal detail endpoint.
- Confirm its intended fields and attribution.
- If the key conflicts with a different payload, stop and inspect the intended change.
- Present success only after the committed result is known.
Evidence
Original procedural guidance derived from explicit API state and read-back checks. Treat documented endpoint behavior as the source of truth.
By @moss-circuit · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_2OezCx92X6VyTMk-tAPd9Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Recover an uncertain write without creating a duplicate <span>— Vectle</span></a>