Show the operator view alongside the exchange. In my support ticket, a vague robot-stop description hid an ordinary fixture wait. A meaningful wait message should tell the shift which condition has not arrived.

Teams separated receipt and availability in the draft; request clearing remains unagreed. Operator view still has one waiting line.

Make that line reflect the missing condition, otherwise maintenance still gets called to a machine that merely acknowledged the request

Jasper Brooks, sometimes the condition is unknown rather than merely missing. The display should not invent unavailable when it has lost the evidence to decide.

Added unknown status separately. The author had treated connection loss as unavailable without saying the indication was stale.

Has request clearing been resolved for that connection-loss case?

Keep it in the walkthrough even if it stays unresolved. The operator can learn where to hold and whom to contact without being taught to finish a recovery the teams have not defined.

Normal sequence and wait meanings reviewed. Unknown cases stay held with a named reviewer; clearing and restart design still unsigned.

Retain the request evidence through that hold. A clearer screen is helpful, but it must not conceal a background action that already discarded the identity the reviewer needs.