FR5 restart with an occupied sleeve pocket

Destination uncertain. Release command was sent, but placement confirmation was not saved.

Can controls distinguish confirmation never received from received but not saved? I mean in the evidence available after restart, not what somebody remembers watching during the run.

Not currently. Both look like the same unfinished row.

Then call that row uncertain and define who reconciles it; moving the save earlier will only move the point where software can disagree with the part.

Jamie, would you show the source and destination identities on the same recovery view? Operators here often know the physical location but not which saved row the programmer means.

Yes, Sam, tied to the interrupted attempt, with the evidence and gaps shown clearly; a pocket number without its tray is especially unhelpful after a change.

Added tray and attempt identity to the draft. Controls still needs to define reconciliation and its checks.

Try that draft with someone who did not watch the stop. Ask them what they believe is known and who they would contact, before judging whether the display is clear enough.