Our 2025 recovery exercise used 12,000 test instructions in an isolated environment. No customer money moved. The application restarted after forty-two minutes, which met the engineering team's opening expectation. At fifty-seven minutes, however, operations could reconcile only 11,040 instructions. The remaining 960 had uncertain processing status. Calling the service recovered at the first timestamp would have concealed the work that still prevented a controlled return to normal processing.
The infrastructure lead wanted recognition for the successful restart. The service owner would not authorise further processing until the uncertain population was understood. I supported that refusal and asked the team to preserve the records instead of clearing the queue to make the dashboard look normal. We traced the interrupted transitions, compared acknowledgements and reconciled the test ledger. Every instruction was accounted for after two hours and forty-six minutes. The longer duration became the result presented to management, alongside the earlier technical milestones.
I approved CNY6.4 million for better status evidence, reconciliation tooling and operating exercises. Four months of planned feature work moved back because the same specialists were needed. Commercial sponsors challenged that delay; they were entitled to see its consequences. I explained the unresolved service condition rather than arguing that an infrastructure project should automatically outrank their requests. The operations team also changed the authority required before releasing held instructions, with risk colleagues reviewing the proposed controls.
A later exercise using an equivalent bounded scenario accounted for all instructions in seventy-eight minutes. That was a useful improvement over two hours and forty-six minutes, but it did not establish that every outage could be resolved within the same period. We retained the scenario, data population and remaining assumptions in the report. I would involve the service owner earlier when setting an exercise's completion criteria. The most consequential finding was not a slow component; it was our initial willingness to use a technical timestamp for a banking outcome it did not yet describe.