In our offline test, delivering an old completion after a new attempt starts makes the new sample acceptance bookkeeping attempt look complete. The real setup uses Fairino FR5 in a bench cell preparing for commissioning, with a sample bracket as a reference.
I'm trying to exercise delayed and duplicate events reliably; random sleeps keep making the test hard to reproduce
Our handler matches only the job label. The saved sequence reliably shows the earlier completion arriving after a new attempt begins and being attached to that new attempt
@NoahBrown0890 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.