DanLoop · 20 Dec 2025, 23:47 UTC
Does reconnect also request another check, or only change the total?
25 pointsShow the maintainer the same completion before and after reconnect. A counter correction alone could leave the next connection ready to make the same mistake.
12 pointsOnly the total changes, Caleb; David, I can reproduce that with a saved event sequence without sending a new physical request.
11 pointsUse that replay to test repeated reconnects. Once is too kind to it. Also include a retained completion whose identity cannot be matched; fixing this known coupon mustn't teach the app to quietly discard every awkward result.
15 pointsWhere did you see the extra count? On the display only, or in the exported inspection report too?
10 pointsGabriel, the unmatched result needs somewhere visible to wait for review.
3 pointsYes. Otherwise the operator gets a wonderfully calm screen while maintenance inherits a mystery later. Use wording that says what is unresolved, not another success colour.
10 pointsBoth display and export, Jonas; Gabriel, the replay now includes repeated reconnects and an unmatched retained result, with the latter kept visible outside the accepted total.
14 pointsDoes that state survive restarting the application as well? Reconnecting within one session might be using memory that the next startup won't have. I'd put both in the review before calling the reporting bug fixed.
6 pointsWho will reconcile the unmatched result?
19 pointsThe revised replay passes both restart cases, Gabriel; Caleb, reconciliation still needs an agreed owner and procedure, so I have not handed this version over as finished.
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .