Author identified request received and fixture available separately in the trace. The summary export keeps only one ready column, using the request field.

Does the raw record retain the fixture-available field for your existing stopped attempt? That could answer more than another video while the summary is being corrected.

It does. Request was received, but fixture available dropped before the wait. Maintainer is checking the mapped physical source for this installed fixture.

Keep that raw interval with its attempt identity. In another report, a shortened export lost the preceding change and everyone focused on the stopped pose. Your corrected summary should retain both fields too.

Maintainer found movement at the availability switch bracket. The fixture designer is arranging its restoration to the intended mounting; author has corrected the two summary labels.

Who checks the repaired fixture with the application afterwards?

Our maintainer and the application author, with the shift lead. They'll use the identified block and fixture from the captured occurrence, and compare the full sequence rather than just watch the switch.

Does the operator's screen get the same separate names? The trace can be perfectly clear while the next shift still reports the old ambiguous ready.

Toby, yes, and the trainer should hear how the shift describes it. Replacing one vague word with two unfamiliar labels may still leave the phone report hard to follow.

Repair and normal loading comparison completed without the recorded drop recurring. Shift lead could identify request receipt and fixture availability on the revised screen. Interrupted-sequence checks remain with the author; thanks, Toby, the operator view had nearly stayed unchanged.

Has the support ticket been updated with what is finished and what still needs checking?