Send them as separate occurrences if both are useful. Say what's missing from each. A tidy-looking package assembled from two stops can persuade support they're seeing a sequence that never happened.
Cannot tell support which UR5e stop my screenshot belongs to
GabrielAbbott0018 · 14 Jan 2026, 23:08 UTC
18 replies
Understood. Clip has the block waiting; screenshot has the message. Neither proves they happened together.
11 pointsIs there a saved event history covering the filmed stop, with enough information to identify it? That is the first place I would look for the missing connection, before asking you for more footage.
13 pointsThere is an export, but its clock is offset from the phone. I haven't matched them.
21 pointsAny distinctive event visible in both? Not just roughly the same time. If somebody corrects the clock by guessing until the desired message lines up, you're back where you started.
5 pointsI had two people film a stop once and neither showed the screen the other person thought they were covering. Very thorough coverage of one stationary part. Worth deciding what the next recording must include before everybody reaches for a phone.
3 pointsWho can recover the application history without disturbing the stopped job?
4 pointsOur controls contact has the saved export. Clip shows a tray-change acknowledgement also present there.
4 pointsHave that contact verify the match and retain the original times with the explanation. The offset may be explainable, but I would not rewrite the raw history to make it prettier.
-2 pointsCallum, yes. We kept the originals after our filming muddle; someone else needed to see what was actually absent, rather than trust our improved version of events.
6 pointsControls matched the tray acknowledgement and following events. Filmed stop says destination unavailable in the application history.
17 pointsThat's useful. Does your separate screenshot say something different, or is it the same wording from another occurrence? Keep its identity separate either way.
5 pointsDifferent wording: tray exhausted. That screenshot is staying separate. I'm asking what destination unavailable means here.
7 pointsGood question for the application owner, not a guess from the stationary block.
10 pointsHas the seller actually received the matched version now, Gabriel? I'd put the difference in the first line, because they may still be answering the old combined report.
3 pointsSent it with separate occurrence IDs. Asked them to retire the combined attachment from the ticket.
10 pointsSeller acknowledged the split and forwarded the filmed occurrence to their application contact. No diagnosis back yet.
16 pointsLeave the other occurrence open in your list too. You might eventually find one cause behind both, but at least nobody now has to explain a fictional sequence made from your two recordings.
22 pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .