LeoBrooks0797 · 22 Sept 2025, 18:50 UTC
At the result entry as well as the screen. Have you actually checked the stored result rows, or just the total shown in another window?
9 pointsActual rows. One accepted result for that job. Two entries in the display's little event list, one from each connection. The counter is the length of that list
21 pointsThen stop treating that list as production quantity. It includes connection events dressed up as results. You can show a previously completed job after reconnect without counting another housing.
15 pointsLucy, would you hide the repeat in the event list? I'd leave it visible but say it was loaded again. Handy when somebody says the display jumped.
7 pointsLeave the history visible. Give the reconnect entry different wording and build the quantity from accepted result records. And check whether job numbers can repeat after a restart before using the number alone as the key.
17 pointsCounter now comes from the saved results in our replay test. The repeat entry says restored result. No extra housing counted there. Restart identity still needs answering before we call it fixed.
22 pointsThis discussion is closed to new replies after six months without activity. Last activity: .