YasminBarnes0528 · 7 Feb 2026, 20:17 UTC
Does the application remember that it already recorded that job, or does it only remember the number on the screen? Those are rather different kinds of memory.
19 pointsIt saves the total but not which completion contributed to it. The PLC still has the job identity. So reconnect reads a real old completion and our app celebrates it again.
24 pointsThen I'd make the classroom test reconnect more than once to that same completed job, and also bring back a genuinely unfinished one. Fixing the duplicate by ignoring everything on reconnect would only give you a quieter wrong answer.
9 pointsDeveloper added persisted completion identity and reconciliation against the retained job. In the lesson harness, repeated reconnects count the completed job once; unfinished and mismatched jobs stay pending review. No automatic resend. Thank you for the unfinished case, Jack.
24 pointsNice. Did they also try a restart after saving the completion identity but before refreshing the screen? That little gap has made our displays confusing before.
9 pointsThis discussion is closed to new replies after six months without activity. Last activity: .