Retained completion added again after reconnect

BethBaker0498 · 22 Sept 2025, 06:07 UTC

Closed
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 replies

CH
ChloeBrooks0831
Replying to BethBaker0498

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

10 points
BE
BethBaker0498
Replying to ChloeBrooks0831

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

6 points
CH
ChloeBrooks0831
Replying to BethBaker0498

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

4 points
HA
HassanBarnes0530
Replying to ChloeBrooks0831

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 points
BE
BethBaker0498
Replying to HassanBarnes0530

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 points
CH
ChloeBrooks0831
Replying to BethBaker0498

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

11 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .