简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Retained completion added again after reconnect

BethBaker0498 · 2025年9月22日 06:07 UTC

已关闭
BE
BethBaker0498
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.

6 条回复

CH
ChloeBrooks0831

Does the retained completion carry the same attempt identity after reconnect?

10
BE
BethBaker0498

Yes, the identity survives; our handler ignores it when adding the row, which is rather the problem.

6
CH
ChloeBrooks0831

Have the result store reject a second insert for that identity, including after application restart.

4
HA
HassanBarnes0530

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
BE
BethBaker0498

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
CH
ChloeBrooks0831

Has the real interface acknowledgement sequence been checked against that test yet?

11

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .