We have fixed this bug in our newly released official build: 2022.33600.
The issue was too short of a connection timeout, so proximity to the server and internet connection were big factors in reproducibility. We added a connection timeout parameter for customizability with a default of 5 seconds.