Skip to main content
Cadet | Tier 2
February 10, 2022
Question

File Trigger works most of the time, not sure if something is timing out, or if its a vm setting.

  • February 10, 2022
  • 11 replies
  • 502 views

I have a vm botrunner with a onedrive synced folder, if a file is dropped in this folder, the bot should be triggered to run.

 

I remote into vm and boot up control room to make sure trigger event is active.

 

I can successfully get the bot to trigger even if vm is unlocked, locked, connected, or disconnected. All appeared to be working, so I disconnect from vm for the day(not sign out).

 

The next day, first thing in the morning, I dropped another file on the folder to see if it would trigger, it did not trigger.

 

I'm new to this, did it not trigger because of a session timeout? Am I missing something else? Please help, thanks

11 replies

Micah.Smith
Automation Anywhere Team
Automation Anywhere Team
July 5, 2023

Hi @Micah.Smith 

we still have problems with triggering on unattended bot runners. We are running A360 v25. 

In your last post you mentioned that triggering today works differently than it did one year ago… Which version did you relate to? And how does it work now?

Triggers previously required that you had a user with a logged in session to the Control Room for operation. This behavior changed in .28 to auto-connecting to the CR for unattended users - https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/release-notes/v28-release-rpa-workspace.html#:~:text=Auto%2Dconnect%20to%20non%2DUI%20triggers%20for%20unattended%20users