LESSON03.370 minutes
Automate a repeated workflow
Design for failure and recovery
Force a failure, prevent duplicates, alert an owner, and finish the work manually.
A workflow is not ready because the happy path ran once. It is ready to learn from only after timeout, bad input, duplicate trigger, partial completion, and manual recovery are visible and rehearsed.
Learning outcomes
What you should be able to show.
- 01Create a failure-mode list
- 02Define retry and duplicate behavior
- 03Rehearse manual completion and rollback
Studio practice
Make the lesson visible.
- 01
Force five failures
Test a missing field, unavailable service, invalid output, repeated trigger, and downstream rejection.
- 02
Make state visible
Record started, waiting, failed, needs review, completed, and reversed states with a named owner.
- 03
Recover without the builder
Give the runbook to another person and confirm they can stop, inspect, complete, retry, or reverse the case.
Evidence to keep
Your lesson record.
- Failure matrix
- State and alert record
- Independent recovery result
REFLECTWhat happens if the same trigger arrives twice while the first run is still waiting?