An old completion closes our newer inspection attempt

I can make our offline FR5 inspection tracker accept attempt one's result as attempt two's result. Both use the same coupon identifier. Random delays only catch it occasionally, which makes a poor handover test. I want to hold the first completion, start the second attempt, then release the old message on demand. Is a queued event test enough, provided it also covers duplicates and reconnection?