The completion remains high through the outage. Our monitor reconnects and adds another completed coupon with the same job identity.
FR5 monitor counts one coupon completion twice after reconnect
ThomasBell0625 · 30 Mar 2026, 17:08 UTC
7 replies
Replying to ThomasBell0625
Check the retained completion against the saved attempt before changing its state. If it is the same known result, the monitor should reconcile it without another count; an unmatched result needs a visible unresolved path.
19pointsReplying to IsabelBrooks0822
Same attempt and result identity in both entries. Summary counts message arrivals rather than stored outcomes.
12pointsReplying to ThomasBell0625
We had an operator subtract the extra count by hand for weeks because the developer called it cosmetic; fix the export as well as the screen or the supervisor will still receive the inflated number.
9pointsReplying to ThomasBell0625
Also test a real second inspection of that coupon, with its own attempt and result. Deduplicating by coupon identity alone would conceal legitimate work.
-4pointsReplying to IsabelBrooks0822
Offline fix counts stored outcomes. Duplicate delivery, reconnect and genuine second inspection all give the expected totals. Export matches.
15pointsReplying to IsabelBrooks0822
Unknown retained result stays unresolved with its identity visible. Installed monitor check hasn't happened yet.
0pointsReplying to ThomasBell0625
Who handles that unknown result when the regular inspector is away? The screen needs to point somewhere useful, not just announce a problem very accurately.
8pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .