Skip to main content

I’m experiencing issues with the Microsoft 365 Outlook triggers for unattended devices.
Everything is properly configured, the trigger worked fine for 2 weeks, then it stopped working. Even if I went into the CR and hit refresh to activate the trigger, it wouldn’t work. I reset the bot agent and it started working again, but only for one day, because today it stopped working again.

Here’s a list of the things I’ve already checked:

  • The VM does not log off, it locks.

  • I already verified that nobody logged into the VM and manually logged off or restarted it.

  • It worked unattended for 2 weeks and then suddenly stopped working.

  • The trigger is correctly configured since when I restarted the bot agent yesterday it worked again (so it’s not a code issue)

 

I’m lost, and I couldn’t find any relevant information in the documentation.

I appreciate your collaboration.

​@leandro.castello I might check the Bot Runner’s logs to see if it was able to process the trigger. I’ll bet, while the system is locked, it’s unable to process the trigger. You can also manually lock the Bot Runner and try to start the Task Bot and see what happens.

If this is running on a schedule, it should unlock the Bot Runner. But if you’re just using a trigger, that might not be the case. The system may need to stay unlocked.

Logs typically found here:  C:\ProgramData\AutomationAnywhere\BotRunner\Logs

Good morning! Thanks for the reply ​@Aaron.Gleason , these days I’ve been reviewing the logs.

On that runner I have 2 triggers listening, one deactivates every 2 or 3 days, the other works correctly.

Both listen to the same email with the same Outlook credentials.

I was able to identify in the log an error message that occurs right before the problematic trigger stops working.

2025-Sep-28 Sun 09:03:02.524 ERROR [Thread-257431] - com.automationanywhere.authsdk.office365.client.CustomHttpClient - performLogging - java.net.SocketTimeoutException: Read timed out

Could you help me with this?

Thanks!

​@leandro.castello This part of the message...

com.automationanywhere.authsdk.office365.client.CustomHttpClient - performLogging

...explains what’s wrong. Unfortunately, this is going to require a trouble ticket. Please send an email to support@automationanywhere.com outlining the issue and including the line above in the log. 

Sorry I can’t help more, but this really must be escalated for further investigation.

Terms & ConditionsCookie settingsAccessibility statement