I'm testing our inspection result reconciliation tracking offline for a setup using Universal Robots UR5e in a workshop fixture-checking station, with a fixture-mounted plate as a reference. An earlier attempt's completion incorrectly completes a newer attempt if I deliver it after that attempt starts.
I need repeatable delayed and duplicate event tests because the random sleeps aren't reliable.
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
@CarlaBarnes0575 How should I handle history when the same completion is delivered twice? I'd expect one count change but still want both observations visible.