I reproduced an FR5 reporting error by holding one completion message until the next inspection attempt had started. Both attempts use the same coupon label. The result closes the newer attempt, which is wrong. I would like a repeatable queued-event test instead of hoping random delays reproduce it. What should that test preserve across a simulated restart?
Delayed completion crossing into the next coupon attempt
JonasBell0633 · 21 Aug 2025, 08:08 UTC
0 replies
Discussion closed
This discussion is closed to new replies after six months without activity. Last activity: .