FR5 sleeve transfer loses its place between release and save

Jonas, yes, the program treats the release command as completion. Anna, the sleeve was in the fixture on this occurrence, but that was found during checking, not confirmed to the program.

That observation can settle this particular recovery without establishing a general rule that release sent means placed. Controls needs to define the receiving evidence and the uncertain case separately.

Give the operator that distinction in ordinary words too. Otherwise the screen says incomplete while the fixture visibly contains a sleeve, and someone will decide the screen is simply wrong.

Felix, should they see the saved pocket and the interrupted destination together?

Yes, Jonas, with their identities. I would not make them remember which fixture the old pocket was feeding while reading an unexplained pending label.

Leo Carter, does the draft also handle a fixture being cleared while the job is held? That changes what a later operator sees without necessarily changing the saved attempt.

Not in the old sequence. We have added it to the recovery review along with the receiving confirmation and a restart during recovery. Unknown attempts remain held instead of returning to the normal tray loop.

Has the controls owner agreed those states, Leo Carter, or are they still proposals? The physical checking route needs an owner as well as a software label.

And who advances the pocket after reconciliation?

States agreed in the draft, Leo Chan, with the shift technician handling reconciliation through the reviewed recovery. Jonas, controls owns the explicit advance after that decision. Offline cases are written but not yet passed.