Our monitor adds another finished housing when it reconnects to an already-high completion. The retained job register names the housing family, not the individual attempt. What should we reconcile before changing the count?
Which FR10 attempt owns the retained housing completion?
JaneBrooks0858 · 2025年12月12日 17:06 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
Have the controls and application owners compare what each side retained, including attempt identity, result and whether that result was already committed. If the family register is all you have, it cannot distinguish two attempts on its own. Keep unknown work held for review.
12分There is an application attempt record, but no matching identifier in the retained PLC data. We cannot assign the old completion confidently. The housing is identified separately for quality review.
5分Does that unresolved status survive another restart?
10分And does the replay preserve the original stored history? Starting with an empty file could make a duplicate look like a legitimate first completion. I would keep the unknown retained case distinct from a known result delivered twice.
2分Those are separate offline cases now. The unknown retains its reason across restart; duplicate-known-result testing is still incomplete. No automatic clearance or resend added to make the warning disappear.
5分Who owns the physical housing decision while those tests continue?
16分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .