简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
ThomasBell0625 · 2026年3月30日 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分Same attempt and result identity in both entries. Summary counts message arrivals rather than stored outcomes.
12分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.
9分Also test a real second inspection of that coupon, with its own attempt and result. Deduplicating by coupon identity alone would conceal legitimate work.
-4分Offline fix counts stored outcomes. Duplicate delivery, reconnect and genuine second inspection all give the expected totals. Export matches.
15分Unknown retained result stays unresolved with its identity visible. Installed monitor check hasn't happened yet.
0分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.
8分