How to use this reference
Editorial lesson: distinguish an atomic transaction boundary from a process spanning independently committed operations. Model completion evidence, compensable effects and irreversible commitments. Preserve recovery progress and repeat-safe corrective actions while respecting concurrent work and business entitlements.
Before reading
- Basic distributed operations, eventual consistency and application state invariants
Context and limits
- Compensation does not guarantee restoration of the original state. It is unsuitable where temporary inconsistency is unacceptable or valid recovery cannot be assured.
- Recovery remains domain-specific and may require human intervention. Repeat-safe recovery steps do not make irreversible commitments undoable or guarantee eventual completion.
- The rendered page displays 2026-04-20; the pinned source metadata says 2026-04-16. The reviewed August 14 and September 28, 2026 changes only update links in this file. These are distinct maintenance signals, not publication or edition-release dates.
- Architecture guidance, not an incident, vulnerability disclosure, implementation audit, bounty claim or testing authorization.
Sources and provenance
- Compensating Transaction pattern Microsoft · reviewed 2026-10-04
- Compensating Transaction pattern source at reviewed revision MicrosoftDocs · reviewed 2026-10-04
- August 2026 idempotent-command link maintenance MicrosoftDocs · reviewed 2026-10-04
- September 2026 related-document link maintenance MicrosoftDocs · reviewed 2026-10-04
Record reviewed 2026-10-04. Snapshot d5550c789111. Open the complete JSON contract.