Receiver clear. I had assumed that meant something after release, but I need the job author to explain its exact use here.

I've been caught by a short wait label covering several checks. Ask the author which condition actually keeps it there, then plan the capture around that. A wider video might help, but it won't show an internal condition nobody has named.

Author has clarified it: the receiver assembly reports unavailable before placement. They want its availability changes and the job's wait entry in the same capture. The last export only had the robot's displayed step.

Include the receiver's own reason for becoming unavailable, if it records one.

Andrew, make sure whoever covers the next occurrence knows how to preserve that capture. We lost a useful event because the relief technician restarted the recorder before exporting it. Nobody had told them its history was short.

Thanks, Priya. Our shift lead has tried the export with the recorder's existing history and can find the receiver events. There is a separate saved copy now. No fresh fault yet.

Can support read that saved copy before you wait for another stop?

Yes, they opened it and confirmed the required channels are present. One label was wrong in their viewing setup; they've corrected that. Next occurrence still needed, but at least we know how to send something they can use.

Did their corrected label also reach the person actually reviewing your ticket? I've had the capture engineer and the answering engineer turn out to be different people.