The devops changed the url and I had to go through some steps to find out what the problem was.

I am passing my credentials as well. So, if it tries with the credentials and it doesn't work, may be try twice, may be three times, then raise an error. I don't know a lot about libraries, but the error that I am seeing is a bit confusing now.

This is also used in automated scenarios and over possible network issues, the retry is built in and is a good compromise - basically making the SDK resilient to network issues. The error you're getting is a failure to connect, unrelated to the credentials...

How do you suggest the SDK know what is the 'right' URL and what is the 'wrong' url?

I see. So, is it same thing when network is slow and there is a mistake in url?

Slow network or network died all of a sudden - you wouldn't want your experiments to fail just because there is a network issue. Once network is restored - everything is sent as it should be to the backend. This is the resilience I was talking about

Regarding mistake in URL - I guess it is your responsibility to keep track of not using wrong URLs. As I said before - How would you suggest the SDK know what is the 'right' URL and what is the 'wrong'...