Detailed logging seems to have made my diagnostic display stick when the folder is busy. Watching a UR5e from the telemetry desk; actual cell controls are separate. I suspect file writes holding things up, but I haven't measured where the delay starts. Network could still be involved.
Where do you record the time a reply arrives relative to the time the file write completes? Put those timings alongside the display update, using one suitable elapsed-time clock in the application. A display pause alone cannot tell you which stage waited. Keep the sample's age visible too, so an old successful reading doesn't quietly become a fresh availability claim while you investigate.