JamieArcher0382 · 7 Aug 2025, 13:28 UTC
What identifies the attempt in those retained values, Jamie, apart from complete being set?
21 pointsA bracket label is present, but the same bracket can be checked again. There is no attempt identifier in the monitor's saved row.
4 pointsThen the label alone won't tell you whether it's a repeated check, and deleting every repeated label would lose real work too.
4 pointsOur screen once put a new time on an old value after reconnect, so I would ask whether yours is an observation time or just when the display woke up
-4 pointsDisplay wake-up time. Controls has the original result still retained, and quality has held the duplicate row for review. No request was resent by the monitor.
5 pointsProposed change now includes an attempt identifier and a persistent list of handled results. The existing ambiguous rows remain separate. Controls and software are testing reconnect and repeat inspection as different cases.
2 pointsInclude a restart between receiving the result and saving the handled entry; that's where the persistent list can still leave you unsure what happened.
18 pointsOur handover got confused because the screen said complete while the paperwork said awaiting review. What does your operator see for an ambiguous bracket now?
8 pointsA review status, Nina, with the bracket identity visible. Naomi, the interrupted-save test is included. Those cases have not finished, so I cannot report the new monitor as verified.
16 pointsThanks for spelling out the timestamp, Jamie; I was wondering whether my old display problem was relevant or just familiar-looking
5 pointsThis discussion is closed to new replies after six months without activity. Last activity: .