FR10 sleeve stop with a readable ending and a missing lead-in

NaomiBarnes0593 · 11 Dec 2025, 20:51 UTC

Closed
NA
NaomiBarnes0593
I have kept the first-message problem from my earlier clip in mind. This FR10 occurrence has a readable wait and fixture identity, but the export starts after the unload request. Support needs to say whether that missing lead-in can still be retrieved.

15 replies

NA
NathanChen1156
Replying to NaomiBarnes0593

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.

17points
NA
NaomiBarnes0593
Replying to NathanChen1156

The export was made with a short selected range. I do not know whether the underlying history still contains the earlier request.

12points
NA
NathanChen1156
Replying to NaomiBarnes0593

Then make that the immediate question. Preserve the original export too, so any wider copy stays distinguishable.

15points
MA
MayaChen1171
Replying to NaomiBarnes0593

Who 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.

8points
RE
RebeccaAli0256
Replying to MayaChen1171

Maya, 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.

20points
NA
NaomiBarnes0593
Replying to MayaChen1171

Our 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.

10points
JA
JamieAdams0121
Replying to NaomiBarnes0593

Could 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.

16points
NA
NathanChen1156
Replying to JamieAdams0121

Include the fitted sleeve fixture in that exercise. A correctly exported sequence from the wrong job will be another perfectly readable distraction.

10points
NA
NaomiBarnes0593
Replying to NathanChen1156

The 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.

6points
MA
MayaChen1171
Replying to NaomiBarnes0593

Did the backup get the instructions too? Easy to lose that job once the immediate copy is rescued.

24points
RE
RebeccaAli0256
Replying to NaomiBarnes0593

And 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.

19points
JA
JamieAdams0121
Replying to RebeccaAli0256

Rebecca'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.

11points
NA
NaomiBarnes0593
Replying to RebeccaAli0256

Maya, 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.

11points
NA
NathanChen1156
Replying to NaomiBarnes0593

Send 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.

9points
MA
MayaChen1171
Replying to NaomiBarnes0593

Will the revised capture instructions give the next clip an occurrence identifier the export can actually match?

6points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .