I watched the PLC send a short inspection request while the application was busy, then the training screen reported rejected when its wait expired; nobody can show me that the application accepted the request, and the ordinary job-interface clearing rules are still disputed (safety controls are separate).
Separate request acceptance from the inspection result. A timeout waiting for acceptance says nothing about the bracket's quality. Then define who owns and clears each part of the exchange.
Take rejected off that timeout path in the lesson draft now. We have been withholding a similar exercise until the normal and interrupted exchanges are agreed. It is a bad habit to teach confidently.
Our reset-button review found the same problem from the other direction: a message action changed job state. Keep the request visible when explaining this timeout, so dismissing the message does not imply the work was cancelled.
Could the operator tell whether to wait or call somebody? Unknown is more honest, but a screen full of honest words can still leave them guessing what to do next.
Isabel's point matters if you add cancellation. A cancellation request needs an agreed response; do not treat pressing cancel as proof the receiver never accepted the inspection.
Hazel, yes. We used a paper screen with the person covering breaks and found the missing action immediately. Cheaper than discovering it during the practical session.
Mei, did your paper example use only information the real screen could obtain? I would not want a beautifully clear explanation of an acceptance state the interface never supplies.
That was a gap we had to fix. The walkthrough must use the actual agreed fields, not give the operator facts only the developers know. Thanks for making the limitation explicit.
Our current screen has no acceptance identity, just a connection indicator; I've asked both owners to define a matching acceptance and its retained information before we draw the recovery page.
Then the connected indicator cannot answer the question. I would show the failed request wait plainly and route it to the named support role until the new exchange exists.
Also agree whether the receiver durably retains an accepted request before the PLC clears it. An acknowledgement that disappears with the application process can leave the sender believing work is owned when it is not.