简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
DineshAli0212 · 2025年10月18日 14:35 UTC
Compare the retained attempt identity with durable result records. I am checking that path on another monitor because reconnect bypassed the lookup there. Remembering the last bit in memory would not cover an application restart.
14分Does this interface actually retain an attempt identity, Dinesh, or only a job description? I would want that clear before copying the approach from Anil's monitor.
12分It retains a sequence value with the result; the application stores it, but startup processes the high completion without checking the stored entry.
7分Test interruption around saving the result too, not only a clean disconnect after everything was recorded.
13分Yes, Jamie. A known recorded result and one whose save was interrupted are different cases. An unmatched result needs reconciliation, not automatic counting merely because the signal is high.
16分What does the operator see for that unmatched case? A count fix alone would not explain why their plate is waiting.
10分The proposed screen shows result awaiting reconciliation with its sequence, separate from the accepted total; the revised lookup and interrupted-save cases are still being tested offline.
22分Also verify the sequence's retention and reuse rules against the real interface. A durable lookup is only useful if an old retained result cannot share its identity with new work.
17分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .