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.
Reconnect turns an old completion into a new one - sample verification tracking
LiamBrown0925 · 5 Aug 2026, 11:34 UTC
4 replies
Replying to LiamBrown0925
Does your trace show completion staying high through the outage? And does the application retain what it already consumed?
14pointsReplying to ElliotBrown0944
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.
20pointsReplying to LiamBrown0925
Replay reconnect offline against a durable job record. Match the retained completion before changing counts; persisting the consumed marker should prevent the repeat.
20pointsReplying to ElliotBrown0944
@ElliotBrown0944 A durable marker needs job identity; persisting a generic consumed flag could suppress a different completion rather than correctly deduplicating this one.
9pointsAdd to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.