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.
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
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.