OscarAllen0271 · 21 Feb 2026, 18:03 UTC
Ask them to point to the condition behind the message in your installed job. Our screen once named the wrong recipe, and everyone investigated the name instead of the wait. What does your clip actually show the connector doing?
11 pointsHeld above the empty receiver. Screen says source empty. The source tray still has connectors in it.
21 pointsWas the source-empty message already there before the connector was lifted?
19 pointsThe physical receiver can be empty while the program is waiting for its confirmation. I would ask support which input or software state it expects at that point, using the occurrence you filmed.
23 pointsInclude the fitted receiver identity beside the job ID. Their explanation may belong to a different insert, even if the robot and part names match.
11 pointsOur packer used to report every pause as tray empty because that was the only phrase on the screen she recognised. When we watched a whole transfer with her, she could describe three different pauses perfectly well. I wouldn't make your loader learn the program to report this, Oscar. A picture of the actual state and the words they saw should be useful to the person who wrote it.
3 pointsYes, Nina. Fix the message if it's wrong, not the person reading it
20 pointsCould the displayed job name itself be stale? Our lab shortcut looked right while launching an older configuration. Worth checking the actual loaded version instead of trusting the title on top.
18 pointsZara, possible, but don't announce an old configuration from that. Oscar has a wrong explanation so far, not a known wrong job.
12 pointsCan the developer match that screen message to a branch in the retained occurrence?
24 pointsAnd who will give the next shift a useful report route while this is being untangled, since they shouldn't need Oscar beside them each time it pauses?
15 pointsDeveloper found the label was copied onto a receiver-ready wait. Correct installed job. Earlier clip cannot show when the label first appeared.
20 pointsWe used a small occurrence card with the message, job and tray IDs. Your shift lead could agree that with support while the screen correction is prepared.
13 pointsThat explains why their source-tray questions were getting nowhere. Have they now specified the receiver history to retain, including the preceding unload, so the next occurrence can answer the actual wait question?
25 pointsYes. Capture request agreed with shift lead. Screen label corrected and checked against the branch; intermittent wait still unresolved.
8 pointsMuch better than asking the loader to translate source empty into something it never said
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .