Our UR5e inspection report adds one housing twice if the application disconnects after saving the result but before acknowledging it; on reconnect the same high completion signal goes through the add-result path again.
Retained completion added again after reconnect
BethBaker0498 · 2025年9月22日 06:07 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
Does the retained completion carry the same attempt identity after reconnect?
10分Yes, the identity survives; our handler ignores it when adding the row, which is rather the problem.
6分Have the result store reject a second insert for that identity, including after application restart.
4分Our fleet report once saved the detail and incremented the total separately, so fixing the duplicate row still left the total climbing; worth checking whether yours does that too
-2分It did; the developer has made saving and counting one consistent operation, and our offline reconnect test now leaves one row and one count, including a restart between receipt and acknowledgement.
16分Has the real interface acknowledgement sequence been checked against that test yet?
11分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .