Automation can handle ordinary cases and encounter situations that require evaluation. The path should recognize the exception and make clear who needs to intervene. Continuing without sufficient information can produce a formally complete result but inconsistent with the necessary work.
I propose to identify the cases that have to come out of the automatic flow and the way they are reported. The person should receive relevant data and know the status of the activity. A generic notification can add reconstruction work instead of facilitating the decision.
Let's imagine an order that contains an unrecognized variant. The system can suspend that case without interrupting everyone else, if the process allows. The route must prevent the order from remaining invisible or being considered completed without verification.
The test includes realistic exceptions and subsequent return to the stream. Quality can be seen in the management of the remaining open activities, as well as in the number of automatic operations. Reliable automation makes its limits understandable and preserves a usable passage when the decision requires a person.