Our FR5 reporting application counts a retained completion again after reconnect. I know an uncertain attempt should not be resent, and nothing here resubmits work. The problem is the count: the accompanying register identifies a recipe, not the individual coupon check. Two rows can therefore look alike without being the same attempt.
Cannot assign the FR5 retained completion from the recipe register alone
ChenAli0181 · 2025年11月16日 02:50 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
回复 ChenAli0181
What else survives the outage on each side: an attempt log, a coupon identity, or only that recipe and completion flag?
24分The application has its previous saved results, but the PLC view currently exposed to it has only recipe and flag. The cell owner is checking whether a separate attempt history exists.
17分回复 ChenAli0181
Then don't deduplicate by recipe. Mark the reconnection interval for reconciliation while the owner establishes what identifies individual outcomes; repeated observations and genuinely repeated checks need different treatment.
9分回复 ChenAli0181
A completion count on our report once looked settled until the physical items were compared. Chen, does the current display tell its reader that the interval is unresolved, or does it still show the duplicated total as final?
5分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .