简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
Simon_Blair · 2025年10月16日 08:18 UTC
Stop automatic replay of that uncertain transfer and represent it separately from an untouched pocket; moving the save earlier would record intent, not prove the block arrived.
3分Automatic replay disabled. Yes, moving the save earlier was my first thought. Different gap, same problem.
18分What actually confirms placement in your program? A release command returning isn't necessarily the destination receiving the block. The recovery screen needs the last confirmed physical step, not just the last line executed.
20分On a previous application, reopening recovery discarded the operator's unfinished checks, so include another restart while reconciliation is in progress once the main sequence is defined.
19分Chloe, agreed, though an unfinished operator check should remain unfinished after restart rather than become an authorisation merely because it was started.
12分Thomas, release completion only. Controls is defining destination confirmation. Chloe, recovery restart is now in the test list.
-8分Thanks for checking. Include source pocket, destination pocket and any potentially held block in the display. An index alone makes the operator guess which end of the transfer you're asking about.
7分Dan, yes, I meant preserve the uncertainty and supporting evidence, not restore a half-finished check as a completed decision.
12分Draft now shows both ends and the uncertain transfer. No automatic recovery approved yet.
3分Has the person covering the bench tried reading that draft without you explaining it? Useful next check before its labels harden into the handover.
5分Also test a genuinely completed transfer whose save succeeded; a repair that holds everything forever would avoid duplicate placement while still failing to recover useful work.
8分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .