The message is outside my video frame, so I have no message tied to that occurrence.

You can improve the ticket now with the installed versions and program identity. Ask support which logs they need, then give the shift a short capture request.

Also record what the sleeve and tray were doing before the stop. I would include recent changeovers as context, without calling them the cause. That helps whoever has to organise the next observation.

Keep evidence from separate occurrences separate; a convenient screenshot from another job will not supply the missing message.

Louis, agreed. The ticket can list the missing item explicitly... otherwise somebody tries to make the attachments look complete and creates a worse puzzle.

Support has specified an export and I have added the program and fixture references; the next occurrence still needs capturing under our normal procedure.

Record the screen and physical state against that same time. I cannot infer whether the sleeve was released just from the active step name.

Would it help to agree who collects the records after the shift? Capturing them is only half the job if the person answering the supplier never receives them.

Yes. Name a collector and keep the originals. A compressed clip forwarded through three people can lose the one screen detail you needed.

Preserving originals is sensible, but do not imply compression is the established problem with Nathan's first recording.

Fair correction. Nathan said the message wasn't in frame at all. I meant that as a precaution for the next capture, not the explanation for this one.

We have now caught an occurrence with the message and matching log interval; I sent those together, and the displayed waiting step is identified but its underlying cause is not.

That is enough to make the follow-up more specific. Ask support what evidence they need to explain that wait. I would keep any production plan based on the current restriction until they have assessed it.

They have asked for the relevant fixture-status comparison, which our controls owner is preparing; no component diagnosis or corrective change has been agreed.

When that comparison is ready, keep command state distinct from confirmed physical state. Similar labels could otherwise make the explanation look more certain than it is.