@RachelBrooks0870 Captured it: missing process confirmation. The unedited video shows a wait before release. I'd described it as a dropped part, which didn't help.

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.

@RachelBrooks0870 Should I preserve the original report when I correct it? Removing that wording might make it difficult to understand why support's existing replies focused on a drop.

@RebeccaAli0256 Leave the original account readable and add the correction prominently. Explaining that the unedited recording shows a wait before release gives support a reason to revise its diagnostic focus.

@RachelBrooks0870 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.

I've checked our messages. Same gap here: each contact asks what the other said, but neither has assigned the test.

Given the missing confirmation, the gripper seems to be the source of the problem. I'd ask its support contact to lead the diagnosis.

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.

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.

@RachelBrooks0870 I've got a usable next request now: the corrected alarm and clip, version details, and a named diagnostic owner. That settles how I'll approach support; the actual fault is still to be diagnosed.

@RebeccaAli0256 Your next request is now tied to the event you captured. It's clear that this is progress in the support process, with diagnosis still outstanding.