MiaChen1166 · 30 Oct 2025, 22:10 UTC
Check the shift login can access the required history. Our walkthrough found one that could not, even though everyone knew which page to open.
19 pointsAsk support to state the event window and signals they need, then have the authorised technician check whether the available history retains that window. Another late export won't improve by being longer.
13 pointsYasmin, both shift logins can view history. Rachel, retention is long enough, but our instruction said export current trace.
20 pointsDoes the original video show when the wait started?
1 pointsWe once sent support the waiting time after an operator had already called maintenance. Plenty of minutes, none of the transition they needed. Ask them to mark the missing event on what you've already sent.
13 pointsFelix, that sounds familiar. A walkthrough using an old occurrence can show whether the instruction gets the right window without waiting for another stop.
24 pointsGabriel, the video starts during the wait. We found the earlier event in history and kept its time beside the clip, without calling them simultaneous.
5 pointsHave support confirm that event belongs to this occurrence before using it as the capture anchor. The job step, fixture identity and sequence should help, not just a nearby timestamp.
22 pointsWas the same fixture still installed when you exported it?
12 pointsYes, Gabriel, fixture N4 throughout. Setup sheet and captured screen agree. Support has identified the expected clamp confirmation as the signal to include.
17 pointsDid that finally narrow the fault, Mia, or have they only narrowed the next capture? Both can be useful, but I'd like to know which one you have.
16 pointsAnd does the instruction explain the capture to the relief shift too? We had authorised access sorted before we found the less familiar person still chose the wrong interval.
11 pointsFelix, capture narrowed, cause unknown. Yasmin, the relief technician will try the revised instruction against this saved occurrence.
9 pointsKeep the operator's account with it. If they expected release while the program was awaiting clamp confirmation, that mismatch may be part of the explanation rather than noise to remove.
20 pointsWhat did the operator expect next?
24 pointsTray advance, Gabriel. That expectation is now beside the wait-step record, not substituted for it.
5 pointsHow did the relief technician get on with the saved occurrence?
3 pointsSelected the intended interval without help. Thank you Yasmin for that check; support now has the agreed window, but has not diagnosed the stop.
22 pointsThis discussion is closed to new replies after six months without activity. Last activity: .