Describe the bug
I'm not 100% sure if this is technically a "bug", but we have noticed a behavior change in how screens are displaying telemetry after a recent upgrade. Occasionally, due to a network interruption or something similar, we see this error message:

(error) { "name": "Request error", "message": "Request error, no response received" }

Presumably, this is caused by some background process fetching telemetry and not receiving a response. Previously (v5.17.1) this issue would resolve itself when the telemetry was successfully fetched. Now (v6.9.1), we have to either manually go through each screen and click "clear errors" or refresh the page to make the screens usable again. This can be quite time consuming and detrimental to operations, especially when we are operating over a VPN and this occurs more frequently.

Again, not sure if this is a bug or if this is the intended behavior, but either way we would like the "old" functionality back.

To Reproduce
Steps to reproduce the behavior:

1. Create screen with telemetry points
2. Wait for network interruption (or create one)
3. See screen go blurry and "Request error, no response received" error appear
4. Resolve network interruption, see that the issue does not resolve itself

Expected behavior
The screen should return to normal after telemetry is successfully fetched.

Screenshots

Environment (please complete the following information):

• OS: Ubuntu 22.04
• OpenC3 COSMOS Version 6.9.1
• Browser: Firefox, Chrome