BenAbbott0022 · 25 Jun 2026, 22:53 UTC
What is the counter reading from: accepted attempt rows, or a saved total incremented as results arrive? Those fail differently.
15 pointsAccepted attempt rows. Restart rebuilds the total from them, including two accepted attempts belonging to the same coupon. The running display had hidden that duplication.
15 pointsSame coupon, twice. Does each attempt already carry the coupon identity, or would somebody have to infer that now?
21 pointsAnd who decides which disposition remains current when a later review changes it, because I couldn't hand maintenance a rule that just picks whichever row arrived last
17 pointsLouis, agreed about arrival order. But choosing one accepted attempt also misses a later withdrawal of acceptance; the item disposition needs its own reviewed history.
7 pointsGrace, both attempts have the same coupon ID. Louis and Leah, quality owns the disposition sequence; the developer is using its current reviewed state, not result arrival order.
3 pointsKeep a coupon with no completed decision in the test as well. Missing isn't a quiet pass.
12 pointsLeah, yes, I was thinking of choosing a current decision rather than an accepted attempt; thanks for making that distinction explicit before it became my misleading handover sentence
13 pointsThe rebuild now gives 183 accepted, nine rejected and five awaiting disposition, matching quality's 197-item ledger. Duplicate and reordered attempt deliveries leave those totals unchanged; history remains available.
7 pointsWithdrawal and reinstatement tests also passed against the ledger, including restart between decisions. The dashboard and export now use that same disposition view. Reconciliation closed.
18 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.