The user interface can be clumsy, especially if the endpoint is offline or has a slower bandwidth. If you can cache the information so the Atera Console is faster for us to walk through the information and just show the last time it updated. such as updating the information every 10 or 15 minutes for patches service states and such. And allow us to manually trigger a refresh if we want to wait for it. Otherwise, it can take 15 seconds or longer to view. For example service, I went in to restart a service on one workstation. It took almost 4 minutes for me to go and find the workstation open up the service manager, wait for it to populate to select the service, and click restart. I believe this can be sped up a lot by caching the data, Most of the services we don't necessarily need Real-time information about their state for general system administration, we already know we need to restart or stop/start the service and the current state doesn't matter. Just having a hint that the service was running in the last 15 minutes is good enough 98% of the time.