ZaraArcher0395 · 5 Oct 2025, 12:56 UTC
Match the retained job state against recorded completions before adding anything, rather than treating first sight of a high signal as a new event
21 pointsDoes the bigger total tell the operator the batch is finished?
10 pointsJamie, it also needs to survive an application restart, otherwise the remembered completions disappear and the same trick happens again
14 pointsYes, persistent accepted-job history, not just the last value seen on this connection
-2 pointsHana, yes, it's used for batch progress. We've flagged the affected total for reconciliation with inspection.
7 pointsCan the operator see that warning without opening the details?
21 pointsZara, don't hide unmatched retained jobs just to stop the total growing; leave them visible for review without automatically resending the inspection
16 pointsUnmatched jobs have a separate review list in the proposed change. Known duplicates won't add another completion.
7 pointsTest a disconnect after the result arrives but before its accepted entry is saved, as well as a clean reconnect after saving
14 pointsAnd please leave viewing that review list separate from accepting what's in it
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .