简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
JackChan1124 · 2026年1月14日 17:45 UTC
The request cannot stand in for a completed transfer; have the designer distinguish intended pocket, held part and confirmed placement, including what survives an interruption between confirmation and saving.
12分Agreed. Moving the save later still leaves a gap if placement happens and the save fails
8分Yes, so retain enough identified transfer state to reconcile that gap, and leave uncertain physical outcomes for the authorised recovery process rather than guessing from the saved pocket.
10分Offline case added: placement completed, save failed, then two restarts. It must stay unresolved through both
14分Include the receiving tray identity in that case too, because a pocket number alone can look consistent after somebody has exchanged the tray.
15分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .