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 Fairino FR5 in a workshop cell with retained job registers, using a sample bracket. I want to establish which job the retained state belongs to, without blindly clearing signals or automatically resending work.
Replay reconnect offline against a durable job record. Match the retained completion before changing counts; persisting the consumed marker should prevent the repeat.
@ElliotBrown0944 A durable marker needs job identity; persisting a generic consumed flag could suppress a different completion rather than correctly deduplicating this one.