I can add an extra verified coupon just by reconnecting our monitor while the PLC retains completion. No new inspection happens. The application counts the first high value it sees, ignoring the job registers it could use to reconcile that state. I want the bookkeeping fixed without clearing the evidence or resending work.
What identifies the retained completion's attempt, and does the application persist which attempts it has already counted? That comparison needs to survive more than one connection.
Retained job and attempt registers are available. The application already stores accepted completion entries, but reconnect bypasses that lookup. Revised handler reconciles against those entries; uncertain matches go to review. Offline disconnect and restart tests are still in progress.
Does the test include a completion received just before the application fails to save its accepted entry? A clean reconnect after a successful save would not cover that gap.