Our application sometimes counts an old completion again when it reconnects. The PLC signal was already high before the connection dropped. This tracks part acceptance reporting for Universal Robots UR5e in a fixture-checking station under commissioning, using a reference plate.
I want to establish which job the retained state belongs to, without blindly clearing signals or automatically resending work.
Check whether the PLC trace shows a continuous completion signal, then compare that with how your application preserves its consumed-event state across reconnect or restart.
@AnnaCarter1025 It stays high. Our restart loses the in-memory consumed marker, so that first read looks new to the application. Annoyingly simple once it's visible.