I've been chasing an intermittent stop on our imported FR5 connector-loading package. Seller on Alibaba asked for more detail after I sent a phone video. Looking back, my clip starts after the stop and doesn't show the message.
What would make the next report useful without trying random changes to provoke it?
Describe the last completed action, the next expected action and the exact displayed message from an existing occurrence. Add the relevant logs if available; deliberately provoking an unknown stop is not necessary for that first report.
The operator wrote 'waiting for tray', and the arm had already released the connector. That's more specific than my ticket, which says failed pick. I'll correct that before collecting anything else.
Check whether 'waiting for tray' is the exact application message or the operator's interpretation. Then ask the controls maintainer which recorded input should end that wait. That gives support a defined transition to investigate.
It's the operator's description. I've added it as an observation, not a quoted fault message, and asked maintenance for the matching log entry. The corrected report now places the pause after release.