Our Alibaba FR10 connector-unloading package stops intermittently; 33 days into the ticket, the seller has my phone clip and wants details, but hasn't said which missing observation would help.
What can be read in the clip at the occurrence: message, active step, or neither? Start with those limits. The installed revisions and fixture identity can accompany it now, but the event evidence needs to describe the same stop rather than a collection of plausible screenshots.
Then the clip is a physical observation, not a complete sequence trace. Was there any separate occurrence time recorded, or would someone have to guess which history entry belongs with it?
That uncertainty should remain visible; I once had to correct a screenshot description because it belonged to another fixture, and matching-looking information would not have made it the same occurrence.
Luis, yes. I'd send the approximate time with the candidate entries clearly identified as unassigned, and ask the technician what could establish a unique match. If nothing can, agree the next capture rather than polishing an uncertain event into a false complete one.
Does that technician have the actual program revision? A step description can change between revisions, and a phone view of the held connector won't tell them which sequence your installed package was using.
For any later normal supervised occurrence, arrange a readable message and step, the preceding action, and the relevant retained history with its clock source. The shift collecting it needs to know not to merge a later stop with this unresolved one simply because the arm waits in the same place.
Attachment access is confirmed, Luis; the technician wants the next occurrence's active-step history, so our capture request is specific now, but this stop is still unexplained.