Our FR10 spacer-loading ticket has been open 34 days. Video shows a seated receiving tray and a waiting job. Support asks for more, but nobody has identified which receiver condition they cannot see.
Then ask support and the integrator to name the required history together. You should not have to guess which of those conditions their next email means.
They identified receiver latch confirmation. The retained trace shows it dropping before the wait. Our phone view cannot show whether the latch is properly engaged.
Callum, yes, and let the job author explain the response too; a real loss of confirmation may be exactly why the job waits, rather than the program needing a way around it.
Excessive play in the latch assembly, confirmed against its service information. Maintenance has arranged the specified repair. Elena Baker, cover knows the hold-and-call route; the screen wording is being made more specific.
And include the ordinary tray exchange in that check, Oliver, because a receiver left untouched for the entire demonstration does not tell your covering operator much about the next changeover.
Has the repaired latch been tried with the trays that gave the recorded stops? I mean the identified trays, not merely another tray of the same colour.
Maintenance and the integrator completed the agreed return check with those trays and normal exchanges. Latch confirmation remained stable. The installed message now names that wait, and cover followed the revised response in the handover exercise. We closed the captured fault with support.