I taught the saved housing-loading job, but each empty pocket brings an operator back to me. The handover explains startup and almost nothing about deciding what happened after an interruption.
Ask an operator to describe one actual pause from the screen. The missing decision will be easier to identify than in another demonstration of the normal cycle.
They know the pocket is empty, but cannot tell whether it was expected to be empty. That distinction is in my program notes, not the operator explanation.
Then get that distinction into the reviewed interface and recovery instructions. Include who handles an uncertain case; your notes should not require your physical presence to become useful.