I am experimenting with triggers, specifically the file created trigger, and I am having trouble getting the trigger to work. I am working in the development environment and have checked out the bot, but nothing happens when I create a folder in the specified location. I can only make the trigger happen when I manually go into the bot and click “Run with trigger”.
I would like for this bot to be triggered without being manually told to listen. Also, I was told that I would need to sign into AA for this to work. Is there a way to have triggers fire without signing into AA first? Our bot runner devices are reset occasionally and I don’t want to have to remember to sign them back so that the triggers will fire.
Thank you
Solved
Question about using triggers with AA
+7Best answer by Aaron.Gleason
A file trigger requires 100% use of a bot runner to watch the file system. This means that the bot runner must be told to watch for file updates and must be signed into your CR, even after being restarted.
Consider your SLA: Do you need a bot to fire off *immediately* when a file is created or can this be done on a schedule? That is the difference between having a dedicated bot runner just looking for file changes or being able to scan for updates on a schedule and do other scheduled things too.
+10A file trigger requires 100% use of a bot runner to watch the file system. This means that the bot runner must be told to watch for file updates and must be signed into your CR, even after being restarted.
Consider your SLA: Do you need a bot to fire off *immediately* when a file is created or can this be done on a schedule? That is the difference between having a dedicated bot runner just looking for file changes or being able to scan for updates on a schedule and do other scheduled things too.
1 person likes this
+8- Most Valuable Pathfinder
- 42 replies
a.Trigger service must be running: The Automation Anywhere Trigger service needs to be running on the bot runner machine. This is what listens for trigger events.
b. Bot deployment: The bot needs to be properly deployed to the Bot Runner device (not just checked out for development).
c.Trigger configuration: Make sure the trigger is configured correctly in Control Room:
Navigate to Bots > My Bots
Select your bot, then click "Add trigger" or modify an existing trigger
Configure the file watch settings properly (correct folder path, file patterns, etc.)
d. Authentication issue: You're correct that authentication is required. For triggers to work without manual login:
Use an Unattended Bot Runner license (not Attended)
Set up a default device credential in Control Room
Configure the bot to run with the default device credential
The reason you need to be signed in is that AA needs credentials to run the bot when triggered. For your situation with devices being reset, you have a few options:
a.Use an AA API to programmatically log in the bot runner after reset
b.Set up auto-login for the device using Windows functionality
c.Create a simple startup script that logs into AA
For production environments, the recommended approach is to use Unattended Bot Runners with proper credential management through Control Room.
Madhu Kumar T S || https://www.linkedin.com/in/madhukumarts/
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.