our fr5 status display waits while the diagnostic folder is busy

The separate trace shows the reply returning promptly, then the display waiting for the file write; we can reproduce the gap with a deliberately delayed test writer using saved responses

What happens to the displayed reading's age during that pause?

And does a failed status read have a separate test? Fixing the writer shouldn't make a missing reply look like a current value.

Maya and Rachel, both matter. I wouldn't solve this with an unlimited queue either. A folder can stay unavailable longer than the test, and somebody has to decide what the monitor does when it can't keep every diagnostic record.

Maintainer and maintenance lead agreed bounded buffering with an explicit recording-gap indication, while status age remains beside the latest valid reading; failed reads leave that reading visibly old rather than reporting a fresh success

Have they kept observation time separate from the later write time in the saved records? Otherwise the faster screen can leave a misleading trend file behind it.

Yes, saved-response replay preserves observation times while delaying writes, and full-buffer cases show the agreed gap; failed reads are covered separately, including startup without any valid reading

Has the normal installed monitor been checked with the change now?

Installed read-only comparison completed: display stays responsive during the controlled writer delay, shows reading age correctly and flags the tested recording gap; maintenance has the buffer policy and failed-read cases, so we've closed the logging stall fix