Our UR5e transfer helper advances the source pocket after pickup. Stop before placement and the next screen starts at the following pocket, with no clear state for the sleeve possibly still held. The training draft calls that resume. I call it missing information.
Does the saved state say anything about the destination pocket? You need to distinguish not picked, possibly held and possibly placed before deciding what recovery can do.
Include interrupted saving in the offline cases as well as interrupted motion. Or rather, a file update failure might leave the same uncertainty even when the physical placement happened.
Developer is adding separate transfer states and routing uncertain ones to the agreed recovery check, not the next pickup. We haven't tested the revised sequence yet. The old resume instruction is out of the training draft.