In our offline test, delivering an old completion after a new attempt starts makes the new inspection result reconciliation attempt look complete. The real setup uses Fairino FR10 in a workshop fixture-checking station, with an inspection coupon as a reference.
I'm trying to exercise delayed and duplicate events reliably; random sleeps keep making the test hard to reproduce.
Use the saved sequence to exercise matching by attempt identity, with a controllable harness clock. Making the ordering deterministic should cover this race condition.
A deterministic replay covers the schedule you give it. Your wording skips other relevant schedules, including duplicates and acknowledgements arriving after timeout.
@PriyaBrown0916 You're right; my coverage claim was too broad. This schedule targets the reproduced mismatch, and the duplicate and post-timeout acknowledgement cases need their own schedules.
@RebeccaAbbott0082 Yes. Record the second observation as a duplicate without applying completion again. You want repeat delivery to leave the accepted result unchanged.
@JaneBaker0510 Idempotence means reapplying the message doesn't change the result again. Recording that it arrived is separate from repeating the completion or count update.