How can I tell whether logging is freezing our FR5 monitor?

Developer added those timings to the diagnostic replay. The response arrives promptly, then the display update waits behind the file write. It repeats when the replay writer is deliberately delayed.

What does the screen show during that wait? If the last reading looks current, that needs fixing alongside the blocked write.

We had a screen that kept its comforting old number while the diagnostic folder stalled. People read it as live because nothing said otherwise. Put the reading's age where they look, not in the very log that's stuck.

Bruno, old value stays unchanged with no age. Aaron, maintenance wants normal summaries plus detailed logging when investigating. We've agreed those modes explicitly now.

When they decouple writing, ask what happens at the buffer limit and on write failure; moving the stall off the display should not create unbounded memory use or invisible lost records.

Emma's right. I would rather see 'record incomplete' than a responsive screen quietly throwing away the evidence I later need.

That can be separate from unavailable reading. Otherwise I'll chase the network when it's the log destination that's failed.

Developer has bounded buffering with an explicit incomplete-record notice on overflow or write failure. Reading age is separate. Slow-writer replay keeps the display updating now, but we still need the failure checks.

Try it with no successful read yet as well. An empty startup and a stale last value can make very different screens confusing.

The first-read failure says unavailable without a made-up previous value. Success followed by failure ages the retained reading. Buffer-overflow and write-failure cases each show record incomplete, and the replay identifies the missing interval.

Has maintenance tried the installed revision from the usual shortcut?

Yes. Installed comparison and maintenance walkthrough passed, including the delayed-writer case. The normal shortcut uses the revised monitor. Thank you, Emma; separating the timings found the blockage without altering the robot connection.