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 · 2025年8月21日 08:08 UTC
0 条回复
讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .