Error Recovery
Error recovery helps people understand what failed, preserve their work, correct the problem, and confidently continue from a known state.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/error-recovery/
01What it means
Error recovery is the interface and system behavior following a failed action. It identifies the problem in plain language, connects the message to the affected place, preserves recoverable data, offers a specific next step, and confirms resolution. It covers input errors, conflicts, permissions, outages, and partial success.[1][2][3]
- 01Failure detectedField, action, system, or partial result
- 02Plain-language explanationWhat happened and where
- 03Preserve workKeep valid input and context
- 04Offer safe actionEdit, retry, undo, draft, support, status
- 05Confirm resolutionShow resulting state and clear stale errors
Recovery covers input errors, conflicts, permissions, outages, and partial success; idempotency prevents retry from duplicating effects.
02Why it matters
Failure is unavoidable in networked products. Recovery determines whether a temporary problem becomes lost work, abandonment, duplicate action, or a support ticket. Accessible recovery makes failures perceivable to keyboard and screen-reader users without forcing them to hunt for what changed.
03When to use it
Use recovery patterns for forms, uploads, payments, saves, authentication, synchronization, and multi-step processes. Design them alongside the happy path, especially where requests may time out, partially succeed, or be retried with financial or data consequences.
04How it works
- State what happened in human terms; do not lead with implementation codes.
- Keep valid input and explain how to correct each affected field or condition.
- Place field guidance nearby and provide a linked summary for long forms; manage focus deliberately.
- Offer safe actions such as retry, edit, undo, save draft, support, or status.
- Prevent duplicates with idempotent operations, then confirm the state after recovery.
05A practical example
An address form returns two invalid fields. The page keeps every value, shows a summary linked to each field, moves focus to the summary, and associates each message with its input. After correction, messages clear and the order proceeds without re-entering payment details.
06Where it breaks
A message cannot repair a broken workflow, unavailable permission, or destructive backend. Automatic retries can duplicate payments or edits unless operations are safe. Moving focus or announcing every small validation change can overwhelm assistive-technology users, so urgency must match impact.
Common mistakes
- Showing “Something went wrong” without a cause or next step
- Clearing the form after failed submission
- Retrying a non-idempotent action without checking whether it succeeded
07Sources
- Understanding SC 3.3.1: Error IdentificationW3C Web Accessibility Initiative · Accessibility guidanceUnderstanding SC 3.3.1: Error Identification
- Error messageGOV.UK Design System · Institutional design systemError message
- Error summaryGOV.UK Design System · Institutional design systemError summary