Which bracket attempt owns the acknowledgement beside our FR10 timeout?

AishaAllen0344 · 13 Jun 2026, 23:53 UTC

Reply to discussion
AI
AishaAllen0344
I'm trying to reconstruct one failed bracket inspection, but the Python, PLC and FR10 clocks disagree and the application reused its job label after restart; what can I establish without assigning the acknowledgement to whichever timestamp looks closest?

1 reply

AN
AnnaCarter1025
Replying to AishaAllen0344

Preserve each source's event order and look for a shared sequence, request identifier or restart boundary before adjusting clocks. An acknowledgement also needs its meaning established: receipt is not completion. If no surviving evidence distinguishes the attempts, leave its ownership unresolved rather than force a nearest-time match.

22 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.