Triggering is only supported for attended automation (don't shoot the messenger, just explaining how it currently works).

The only way triggering can work is if that bot runner user is logged in to the Control Room via the web UI FIRST before the trigger is "active" in order to run.

If you believe that triggering should work as a feature of unattended automation, please share that feedback and I'm happy to re-iterate that with the product team.

As an alternative in the meantime, I might suggest scheduling the bot to run every X amount of time to check for files in the directory you're attempting to monitor...in this way, you don't tie up a bot runner with scanning that directory all day, and you can still schedule/run other stuff on the same runner.

Hi Micah,

This is a common use case where customers drop file into a shard/onedrive folder and a bot getting triggered in an unattended fashion and consuming the file. We should take this to our PM team and get this feature included in future releases.

@Eric Sullivan​ I have dealt with the same issue and went bonkers with troubleshooting. After much back and forth with AA support, it eventually ended up with the understanding that the VM "apparently" does not lock and that we'd have to use their suggested solution of a batch file to lock-and-disconnect the VM, although I disagree with them. You could try.

https://apeople.automationanywhere.com/s/article/Batch-file-to-lock-and-disconnect/p>

Thank you Micah and Nidhin, this would be a great feature to have in the future.

Hi @MICAH SMITH​ ,

I see this answer was posted 7 months back. Is it still the case that trigger is only supported for attended automation?

Still the case as of right now - I've raised it up with the product team and they're aware of the limitation. In the meantime, your best other approach may be a python script that continuously executes on a machine at startup monitoring a network share for files...sleeping for X amount of time between checks

Thanks Micah

@Micah.Smith We are unable to pass variables in file paths while using trigger. is there any work around for this.

This is a year old thread @RajeshS106234 - Triggering today works differently than triggering did over a year ago. I’d recommend opening a support ticket if there’s functionality that isn’t working for you - and the team there can work with you on a resolution 

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