Classify failures and recover partial work
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
Temporary network failures may be retried with bounded backoff; invalid credentials, missing required data or rejected permissions usually need intervention. Partial completion requires a deliberate recovery plan. A compensation action may undo some effects, but it cannot erase a message already read. Record what succeeded and avoid restarting every step blindly. Route poison messages that repeatedly fail into an owned exception queue. Limit retries to prevent cost or contact storms. The recovery plan should preserve the candidate’s current intent and the truth of what has already happened.
Worked example
A workflow creates a calendar event but fails to update the ATS. Recovery links the existing event to the application instead of creating another event. If the interview has since been cancelled, it reconciles cancellation too.
Put it into practice
Build a failure matrix for six cases with retry, pause or compensation decisions.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Distinguish transient, permanent and ambiguous failures. Include an external action that cannot truly be undone and explain the corrective communication needed.
Sources and further reading
Original Academy teaching and fictional examples. These references provide context, not endorsement. Edition 2026.09; updated 2026-09-24.
- GOV.UK: Responsible AI in recruitment
UK guidance on procuring and deploying recruitment AI.
- NIST: AI Risk Management Framework
Voluntary framework for organising AI risks and controls.