Automation Fallback Planning: Errors, Retries and Recovery

Lister les interruptions.

Considérez les entrées manquantes, les systèmes indisponibles et les sorties qui ne peuvent pas être acceptées. Décrivez ce qui arrive au travail déjà en cours lorsqu'une dépendance échoue. Faites la distinction entre un retard temporaire et un cas nécessitant une décision commerciale, afin que le flux de travail ne traite pas chaque interruption comme une nouvelle tentative automatique.

Conserver un itinéraire manuel utilisable.

Identifiez les informations dont une personne a besoin pour poursuivre la tâche en toute sécurité. Rendre visibles les travaux en attente et les actions terminées pour éviter les traitements en double. Discutez de la manière dont l'itinéraire manuel sera répété pendant le projet pilote plutôt que de supposer que quelqu'un pourra reconstruire la tâche lorsque l'automatisation s'arrêtera.

Examinez la propriété de la récupération.

Attribuez la responsabilité de résoudre les exceptions et de décider quand le traitement automatisé peut reprendre. Enregistrez les contrôles nécessaires pour concilier le travail manuel et automatisé. Une solution de secours doit faire partie des instructions d’utilisation du flux de travail, et non un document distinct que personne ne sait consulter.

Work through failure before expanding the workflow

List where a task can fail: input validation, an unavailable dependency, an uncertain result or a partially completed action. For each point, determine whether the system knows that nothing happened or whether the outcome is uncertain. That distinction affects whether a retry is safe.

Describe the manual continuation route and the information needed to use it. Assign an owner to unattended failures and agree how they are visible. Test interruptions at different stages, including recovery after a service becomes available. Reconcile the final state so a task is not lost, repeated or left permanently pending. Keep fallback instructions close to the operating workflow rather than only in a development note.

A fallback and recovery decision sheet

Use a row per failure category. Confirm the proposed response with both the business owner and the technical operator.

• Failure point: input, dependency, processing step or downstream action that may fail.
• Known state: what has definitely completed and what remains uncertain.
• Automatic response: stop, retry, defer or reject, with conditions and limits.
• Manual response: responsible role, context provided and available continuation actions.
• Communication: useful user status, operator notification and escalation when unresolved.
• Reconciliation: how the team confirms the eventual outcome and prevents duplicate work.

Do not retry every failed action in the same way

A repeated read and a repeated payment instruction have different consequences. Identify actions that need duplicate protection or a status check before another attempt. Keep error messages useful enough for the operating team to distinguish rejection from uncertainty.

Avoid a manual fallback requiring information the system has discarded. Preserve the necessary context within the approved access and retention arrangements. A queue of failed tasks also needs ownership; making errors visible without assigning a response does not complete the recovery design.

Should a fallback always be automatic?

No. Some failures are better paused for a person, particularly where the next action could create an irreversible or duplicate outcome. Choose the response around the task’s consequences and the information available, then verify that the operating team can carry it out.

ILLUSTRATIVE PLANNING EXAMPLE

Example: an unavailable external service

An automated workflow sends a request to an external service that times out. Decide whether retrying is safe, how duplicate actions are prevented and when a person is notified. Provide enough context for the person to complete or cancel the task without starting again from an unexplained error message.

Test the fallback with the operating team. Record the retry limit, escalation owner and reconciliation step before increasing the workflow’s scope.

FURTHER READING

Official resources to explore

Explore the related official guidance below. The templates and examples are practical starting points to adapt to your own project.

• NIST AI Risk Management Framework Playbook