An application resumes operation while its connected systems still disagree. Include reconciliation in recovery rather than treating a successful connection as completion.
Define authoritative values
Assign ownership for status and identifiers. Identify manual corrections already used by the business. Competing updates require an explicit conflict rule.
Reproduce interrupted exchanges
Test delayed messages, repeated events and missing objects with permitted data. Keep rejected work discoverable. A retry needs to avoid unintended duplication.
Allocate corrections
Ask for a report comparing relevant objects and their relationships. Name the team that resolves exceptions. Requirements specific to your organization should be reviewed by competent internal owners. The delivery mandate should include this operational process, allowing recovery to be judged on usable records rather than traffic between systems.
Related reading : A failed software rewrite: assess reusable work before starting again. Discuss your project scope with Sky Vaults.