LEARN. PRACTICE. GROW.Concept and mechanism
Continuity should be measured against the service used by the business. Starting servers is a technical milestone; recovering a flow includes resuming consistent processing, handling pending work, and confirming outcomes. Observability should combine arrival and processing rates, pending volume, item age, rejections, and business commitments. If 120 messages arrive per minute and 100 leave, the queue grows by approximately twenty per minute while those rates continue. A running process does not prove sufficient capacity. Limits and cutoffs in these exercises are fictional flow agreements rather than universal Swift values. The team should understand drain capacity and delay effects on downstream applications.
Guided application
In a recovery rehearsal, test people, procedures, access, and reconciliation alongside components. Record time to restore the agreed function and problems encountered. A useful runbook identifies references, states, diagnostic steps, action boundaries, contacts, and evidence to collect. Having the support shift execute it reveals knowledge still dependent on authors. Operational handover needs acceptance criteria and clear responsibilities. During an incident near cutoff, communicate scope, age, known states, uncertainty, and required decisions, with a scheduled next update. Do not promise completion merely because servers are available. These exercises apply public recovery concepts; they do not represent a particular bank’s internal procedures.
Example: infrastructure starts in eight minutes, but reconciliation finishes at 23. The rehearsal result should distinguish those milestones and compare them with the agreed functional objective.
Common pitfalls
Component RTO treated as service RTO; deletion-empty queue treated as recovery; project presentation treated as proof of autonomy; uninterpreted logs treated as impact communication.
Related topics: Messages, services, and financial outcomes · Identifiers, relationships, and reference data · States, reconciliation, and recovery without duplication
Delivering autonomy means demonstrating that support can investigate and recover the flow.
Reference: Operational Services · DR Swift knowledge assessment2026.10; independent professional curriculum