Our application sometimes counts an old completion again when it reconnects.
The PLC signal was already high before the connection dropped.
This tracks sample verification tracking for Universal Robots UR5e in a fixture-checking station under commissioning, using a sample bracket.
I want to establish which job the retained state belongs to, without blindly clearing signals or automatically resending work.
@MayaBaker0475 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.
@TheoBaker0497 The trace confirms completion remains asserted through the outage. Our application loses its consumed marker on restart, causing the first read to be interpreted as a fresh completion.