ISSUE-47974: Fix bad logging use log4j instead of printStackTrace()
Using log4j.error as usual instead of manual / bad printStackTrace
As of 2024-05-14 a change has been implemented to enforce access token expiry. If you see higher numbers of HTTP 401 responses, please check tokens that may have expired. For more details, including how to mitigate disruption, please check our docs guide on Expired Access Tokens. If you have a support contract, you may open a support ticket for additional assistance.
Using log4j.error as usual instead of manual / bad printStackTrace