NaomiBarnes0593 · 11 Dec 2025, 20:51 UTC
Ask the person who made the export whether the earlier events were excluded by its range or are no longer retained. Those are different problems, and support cannot recover either by enlarging your video.
17 pointsThe export was made with a short selected range. I do not know whether the underlying history still contains the earlier request.
12 pointsThen make that the immediate question. Preserve the original export too, so any wider copy stays distinguishable.
15 pointsWho has access to make the wider export on your other shift? We lost earlier events while waiting for the only person who knew the menu.
8 pointsMaya, familiar problem. A capture plan that says ask maintenance can still mean ask one particular person who is off. Naomi needs a named backup, not just a department.
20 pointsOur shift technician has access, Maya. I have asked them to preserve the available range now. The backup person needs the export instructions, which were not in the handover.
10 pointsCould the backup person try those instructions on an existing event? That would show whether the right job and occurrence can be found before another stop makes it urgent.
16 pointsInclude the fitted sleeve fixture in that exercise. A correctly exported sequence from the wrong job will be another perfectly readable distraction.
10 pointsThe wider copy is preserved and contains the unload request. The technician has identified the job version and sleeve fixture with it. Support has not interpreted the sequence yet.
6 pointsDid the backup get the instructions too? Easy to lose that job once the immediate copy is rescued.
24 pointsAnd Naomi, do the video and wider history clearly refer to the same occurrence? I'm asking about the match, not whether their clock displays happen to agree.
19 pointsRebecca's distinction matters. An operator note identifying what was being unloaded may help with the match, but it should not be silently treated as a missing event in the controller history.
11 pointsMaya, the backup walkthrough is arranged. Rebecca, two unload waits occurred in the wider range and we cannot confidently assign the phone clip to either. I have told support that explicitly.
11 pointsSend both candidate sequences with that uncertainty intact. They may still explain useful behaviour, but do not splice the video into one because its time looks closer.
9 pointsWill the revised capture instructions give the next clip an occurrence identifier the export can actually match?
6 pointsThis discussion is closed to new replies after six months without activity. Last activity: .