Module 5 of 8
Exception handling
Controls, queues and manual overrides.
Now handle the cases that broke your original process map. Anything the workflow cannot confidently handle goes to a review queue with the reason attached, rather than being guessed at or dropped silently. A queue somebody checks is a feature; a silent failure is an incident waiting to happen.
Build the manual override before you need it. Someone must be able to stop the workflow, correct an item and push it through by hand without a developer. If that path does not exist, the first bad day ends with the whole automation switched off permanently.
Takeaway
Uncertain items go to a review queue with a reason. A non-technical person must be able to override and stop it.