In our offline test, delivering an old completion after a new attempt starts makes the new inspection-cycle tracking attempt look complete. The real setup uses Fairino FR10 in a sample inspection setup with recorded job events, with a reference housing as a reference.
I'm trying to exercise delayed and duplicate events reliably; random sleeps keep making the test hard to reproduce.
Replying to CalebAdams0145
Can you preserve that failing delivery sequence and check which identifier the handler uses to match completion: the specific attempt or only the job label?
11 points