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 workshop fixture-checking station, 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
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?
@JuliaAli0239 Replay that sequence with explicit attempt matching. Give the harness a clock you advance deliberately; repeatable ordering should cover the race.
Fair. I meant this reproduced wrong match, not the whole class. Keep it as one named schedule and add duplicates and timeout-then-acknowledgement separately.