LuisBarnes0608 · 11 Jun 2026, 13:09 UTC
What identifies the job beside that retained signal, Luis, and does your application remember which result it already recorded when the connection goes away?
6 pointsThe PLC keeps a job number. Our application forgets its last recorded number on restart. Reconnection alone can also trigger the display's completion handler.
21 pointsI'd separate reading the current snapshot from accepting a newly matched result, and retain the processed-result identity somewhere a normal application restart doesn't erase it
14 pointsCheck number reuse too. Remembering yesterday's number won't help if today's housing gets it again
1 pointsAnika, the number resets with a new run. Gabriel, our current handler doesn't distinguish snapshot reads. Two separate holes, then.
22 pointsYes, and I would give the developer the reset example as well as reconnect, because keeping a number permanently can create a different mistake when that number is reused
21 pointsDon't make an unknown run look like a failed inspection either. Unknown means you haven't reconciled it
12 pointsThe replay now leaves an unmatched retained result pending reconciliation. Same-run duplicates aren't counted twice. Run changes still need a defined identity from the PLC team.
22 pointsThanks for stating which part is still missing, Luis; whoever takes over the monitor will need that distinction, not a note that reconnect is fixed
25 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.