Time, yes. Message unreadable. I can send program and fixture details now.

Ask someone on shift to capture the next ordinary occurrence under your approved procedure. Include the sequence just before it stops, because a static view of the arm can fit several explanations, even when the symptom feels obvious in person.

We have called them all stops. No consistent message recorded so far. Capture plan now with shift lead.

Keep the investigation within the existing operating restrictions; the capture request should not encourage anyone to provoke the stop or alter safety functions for a clearer film.

And let the lead know what evidence can be gathered without another occurrence: versions, recent approved changes, normal sequence description. Waiting for the perfect clip can waste days on information already available.

Ravi's right. I focused on the next occurrence, but Caleb can send that background now and have the missing message listed as outstanding. It needn't be one giant finished report before anybody responds.

Background sent. A new clip and matching export now show a particular wait. Earlier stops remain unclassified.

What does that wait describe: a requested fixture condition or confirmed feedback? The screen name alone may not tell you why the sequence remained there.

I don't know. Support asked our controls owner for the fixture-status comparison.

Has anyone linked this occurrence to the original clip, or should those remain separate in the ticket?

Separate, Sarah. Thanks; I'll keep the first clip listed without a diagnosis while controls checks the new event.