[Bug]: No server accessible for minutes if one server is unreachable

[abravetti]

Checks before filing an issue

• This issue doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
• I have checked the issue tracker and have not found an issue that matches the one I'm filing. This should include closed issues.
• This issue is not a troubleshooting question. Troubleshooting questions go here: https://forum.mattermost.com/c/trouble-shoot/16.
• This issue is not a feature request. You can request features and make product suggestions here: https://mattermost.com/suggestions/.
• This issue reproduces on the most recent stable version, or the most recent prerelease version of the Mattermost Desktop App.
• I have read the contribution guidelines.

Mattermost Desktop Version

Version 5.11.2 commit: 831f0c7

Operating System

Pop!_OS 22.04 LTS

Mattermost Server Version

Two servers, both 10.2.3 db 127 build 12917686922 on postgres

Steps to reproduce

• Configure you Mattermost desktop app with two server: Server A and Server B.
• Shotdown Server A (or disconnect a VPN if used, or make it unavailable).
• Restart Mattermost desktop.
• Notice that you can't access also Server B for more than 2 minutes.

Expected behavior

It should work for the working servers and give some error only for the unavailable server.

Observed behavior

If you have multiple servers and one server fail, during the application start, the whole application is unusable for a long time, more than 2 minutes.

If the server fail after application start, then the behavior is normal and you can work on the working servers.

This problem was not present on 5.10.* and seems related to 5.11.2.

Log Output

can't add the log now, I will add it later.

Additional Information

No response

[abravetti]

In this case "Server A" is working while "Server B" is not available.

It will remain more than 2 minutes as in this picture:

[devinbinnie]

I can't reproduce this, is it only happening with the one server? Have you tried with both a local instance that you shutdown and a VPN instance?

Logs would also really help here.