FR10 housing stop with two different event windows

No, they asked for the fault log without naming an event or window.

Send them the readable waiting message and the two time ranges, then ask what preceding transition and signals they need to interpret it. A longer export might help, but only if it contains the relevant occurrence.

The message is waiting for housing seated; both ranges are now beside the original clip in the ticket.

And which physical nest is that message referring to?

Include its fitted insert too, if the nest takes more than one.

Nest N3 with insert B is confirmed for this occurrence, and support now wants the request and seated-state changes preceding the wait.

Can maintenance still retrieve that period? Some history is only useful if somebody exports it before it rolls away. A precise request arriving late can still leave you with nothing to send

Isabel, exactly. Mia, is the original history retained anywhere?

The local history has rolled over, but maintenance retained a full copy from that session; the first export was only a filtered view.

That is fortunate. Have maintenance check the retained copy against the requested window, with the filter settings clear. I would keep the unfiltered original too, rather than let the next selected view replace it.

Thanks for distinguishing the full copy from the first export. Easy to miss that difference.

Maintenance supplied the requested range from the retained copy; support has acknowledged it and assigned a technical contact, but has not explained the missing seated confirmation yet.

Does that contact have the N3 and insert B details with the extract? Worth keeping them together when the ticket changes hands, since a correct time window cannot identify the physical setup by itself