our ur5e spacer wait has a request nobody seems to receive

Only the app message so far. I've asked its author to explain that.

Can both authors identify the ordinary request and receipt signals and who owns them until the exchange is complete?

They sent the interface notes. App briefly asserts request, then clears it without waiting for receipt.

Does the captured fixture record include that brief request?

Ask them to walk the missed-receipt case together. We had two suppliers demonstrate their own ends of an exchange successfully, then spend a meeting blaming the gap between them. One sent a brief indication; the other expected it to remain available until acknowledged. Both screenshots looked perfectly respectable. What finally helped was making them explain who kept each state, what confirmed receipt and what happened when the other side was absent.

No request in the fixture's captured interval, Anika. Authors are checking the actual exchange, not just the screenshots.

Keep that absence separate from proof of why it was missed.

Have they reproduced the short-request case in a controlled interface test with both ends observed?

Yes. Their test reproduces a missed request when the receiver checks after it has cleared.

What change are both authors agreeing?

Request retained until identified receipt, with timeout shown as unresolved rather than silently clearing and sending again.

Include late receipt after timeout. It still belongs to the original request.

And ask what the operator sees while it is unresolved. Somebody still has to explain why the job is waiting without inviting a second request to make the message go away.

The revised display names the unresolved request and directs the operator to the shift lead.

Does the lead have an agreed decision process?

Yes. It includes checking retained receipt evidence with maintenance, not assuming timeout means nothing happened.

Does the proposed exchange survive either application restarting without reusing an old receipt for a new request?

Offline tests passed for delayed receiver, lost connection, late receipt and either restart, using distinct request identities.

Installer completed the agreed station checks. Our spacer job no longer loses that request. Operators used the revised waiting explanation.