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.

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

@CalebBennett0754 On my setup, the arm and gripper contacts both thought the other owned the test. Naming one coordinator helped us get an actual next step.

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.

@DavidCarter1041 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

@CalebBennett0754 I now know how to make the support request actionable: provide the corrected event description and version details, then ask for diagnostic ownership. This resolves my reporting question while leaving the underlying fault open.

That answers the reporting problem without claiming a repair. The corrected symptom gives the next request a useful focus