@Leeann #p3067 Thanks for sharing the job details. I took a look and verified the failure is happening during authentication. This credential type uses static credentials, so it won’t show a warning or prompt to reconnect if the saved credentials are no longer being accepted.
I also found a secondary authentication message in the bot that was being masked by the more general error. Which is an “Invalid email or password.”
Could you please double check the email and password saved in the connected account? Updating those credentials should resolve the issue
