Nothing at present; its timer clears the request regardless of whether the application saw it, and the application author had assumed the PLC held it until receipt.

Put that disagreement into an example both authors walk through. The request needs an identity and an agreed receipt, with each side owning its own state changes, not a longer hopeful pulse.

What does the operator see while receipt is missing, Naomi? That wait should not look like an inspection already under way

The authors agreed a retained identified request until matching receipt, with receipt separate from inspection result; the revised screen says waiting for request receipt, and their offline delayed-receiver test no longer loses the request.

Did they test a repeated receipt and restarting either side?

Yes, repeated receipt starts no second inspection and the restart cases retain the outstanding identity for reconciliation; the application owner repeated the agreed checks on the station and the trainer followed the new waiting explanation.

Useful. Keep both program versions with that interface revision so the next update doesn't quietly put the two authors back in different conversations