简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
QuinnBlair · 2025年11月9日 12:48 UTC
Keep that uncertain transfer out of automatic restart, Quinn; which observations can currently establish whether the sleeve is in the tool, source fixture or destination?
17分Destination uncertain. Release command was sent, but placement confirmation was not saved.
20分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.
15分Not currently. Both look like the same unfinished row.
21分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.
20分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.
9分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.
9分Added tray and attempt identity to the draft. Controls still needs to define reconciliation and its checks.
8分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.
20分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .