ThomasBell0625 · 30 Mar 2026, 17:08 UTC
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.
19 pointsSame attempt and result identity in both entries. Summary counts message arrivals rather than stored outcomes.
12 pointsWe 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.
9 pointsAlso test a real second inspection of that coupon, with its own attempt and result. Deduplicating by coupon identity alone would conceal legitimate work.
-4 pointsOffline fix counts stored outcomes. Duplicate delivery, reconnect and genuine second inspection all give the expected totals. Export matches.
15 pointsUnknown retained result stays unresolved with its identity visible. Installed monitor check hasn't happened yet.
0 pointsWho handles that unknown result when the regular inspector is away? The screen needs to point somewhere useful, not just announce a problem very accurately.
8 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.