The retained record has a unique attempt identity and coupon link. Our saved detail row already contains that result once, but the displayed total increments when the monitor sees high after connecting.

Then fix the total's source rather than disturb the PLC state to make the screen's arithmetic behave

Does the total mean completed attempts or accepted coupons? The same stored result can support a technical completion count without establishing the coupon's current quality disposition.

Replay the saved records first. Can the expected total be rebuilt without a live connection?

Include a completion first discovered after disconnection too. Reconnect must not add a duplicate, but it still needs to record genuinely new identified results that arrived while the monitor was absent.

And reopening should derive the same result, not restore yesterday's separate counter from another file

Both pass in the replay: repeated retained result stays one row, and a newly discovered identified completion adds one row and one completed attempt. Reopening rebuilds the same total. The old standalone counter is no longer read.

Have those tests used the actual retained-record format from your documented interface? A convenient fake identity would test the counter while leaving the real input path unexamined.

Yes, saved records from the installed interface, then the maintainer repeated the reconnect comparison through the normal monitor. Counts match the durable rows after reopening. Thanks Anna; the screen label remains completed attempts, not accepted coupons.

Keep that distinction and the newly discovered-result test in the handover. The fix now accounts for both replayed history and work first observed after reconnect, without changing the job's physical state.