Shutting down a self-hosted server outside of Prisma Cloud prevents you from using the Console

[marktani]

Describe the bug

When you shut down a self-hosted server that is connected to your Prisma Cloud account, you cannot use Prisma Cloud anymore.

To Reproduce Steps to reproduce the behavior:

1. Go to https://app.prisma.io/<workspace>/servers/add-server, and use "Connect to a server"
2. enter the URL to a self-hosted server that is currently running, and finish the wizard.
3. Shut down the self-hosted server.
4. Go to https://app.prisma.io/<workspace>/servers
5. Endless loading. Open dev tools and locate one request to api.cloud.prisma.sh which returns this error:

Cannot return null for non-nullable field Cluster.version.

Expected behavior

I suggest the following:

• The Cloud API should return a human-readable error, something like "Server not reachable"
• The Prisma Console should handle self-hosted servers that can't be connected to gracefully - one error from one server should not cause the entire Console to fail.
• The Console should print "Connection error" or similar for those servers that can't be connected to.

[marktani]

This is now resolved.