I now have the alarm indicating a missing process confirmation. Reviewing the unedited video places the wait before release, so my original description of a dropped workpiece was inaccurate.

Correct the ticket with that alarm, the unedited clip and the installed versions. Ask which confirmation is missing and who owns the next diagnostic step.

Worth leaving my original description visible? It's wrong, but deleting it might make the replies look odd.

@SofiaAdams0108 Keep it with a clear correction. Explain that the full clip shows a pre-release wait; that tells support why the investigation needs to change direction.

@MinaBaker0511 My own support case stalled because the robot and gripper contacts each expected the other to arrange the test. A named coordinator clarified who would organise the next action.

@MinaAllen0337 Our correspondence shows a similar coordination gap. Both contacts refer me back to the other's response, and I can't find an assigned owner for the test.

That missing confirmation points to the gripper, so its contact should take the diagnostic lead.

You're jumping from a missing signal to a failed component. It could be the interface or sequence. The alarm doesn't assign ownership by itself.

@MayaChen1171 You're right; I assigned the cause too early. Ask the package seller to coordinate tracing that confirmation across the interface, with both contacts involved as needed.

Is that Alibaba support, then? i'm muddling the seller and the place you bought it.

I mean the business that sold you the package through Alibaba. The marketplace and that seller have different roles; this technical coordination request goes to the seller's support arrangement.

@MinaBaker0511 I have several logs but haven't established which capture the event. Is sending the entire collection useful, or should I narrow the attachment set?

Ask which diagnostic files they need and provide the ones you can tie to the event. Include collection context; unrelated bulk can hide the useful bit.

In my support case, descriptive attachment names made it easier for both support and me to locate the relevant recording. Generic revision names had made the collection unnecessarily confusing.

Guilty of the 'final' filenames. I also cut the original clip too tightly; it lost the wait leading into the alarm.

@SofiaAdams0108 Attach the full recording even if you include a short excerpt to highlight the symptom. The lead-in you found is relevant to understanding how the alarm arose.

@MayaChen1171 Should they keep reproducing it until support can watch? Or is the captured event enough to start with?

Start with what's captured. Any further equipment test needs a defined procedure from the responsible support or integration person, especially with a workpiece still held.

I'll make the next request specific: assign a diagnostic owner, identify the confirmation to trace and list the required files. That should give me a concrete action to carry out.