Description

Currently, when a request is failing due to a an HTTP error, a read error, or another request error (not platform error or rate-limiting error), its very hard to know this during development.

The reason is that the default retry policy allows retries for up to 30 minutes. This is useful in production, which retrying is more likely to give your app resiliency to production issues on either your side or Slack's side. However, in development this just impedes your ability to understand a failure ever occurred.

I recently faced this issue when using a custom TLS configuration. This was causing an error, but since I did not have DEBUG logging enabled, I had no idea the request was being retried.

The proposal is to change the log level of this line to warn and to add information about the error:

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.