Skip to main content
Solved

Can an AARI Process run on a specific BOT Runner?

  • January 31, 2023
  • 5 replies
  • 307 views

Forum|alt.badge.img+9

We have a requirement for our BOT to run on a specific BOT runner. Is it possible to configure an AARI process or a BOT that’s called within an AARI process to launch on a specific runner? If so, what are the steps to accomplish this?

Best answer by Padmakumar

Hi @JMarino & @Rob B .

 

Yes, an AARI Process can run on a specific BOT Runner. It is possible to configure an AARI process or a BOT that’s called within an AARI process to launch on a specific runner.

Here are the steps to accomplish this:

  1. Use the admin account and go to your Scheduler user role.
  2. Click on Edit.
  3. In the Bot section, give access to all Bots.
  4. In the Run-As section, select the runners in your Device pool.

 

Please note that bots executed through AARI Web are run on unattended Bot runners - using a device pool.

 

Please refer the below blog on the same.

Tech Talks: What is AARI? | Community (automationanywhere.com)

 

 
 

5 replies

Rob B
Forum|alt.badge.img
  • Cadet | Tier 2
  • December 6, 2023

Hi @JMarino did you end up resolving this? I am looking to do the same at the moment.

 

I am thinking that a custom role for a specified user with the AARI Scheduler, Schedule My Bots permissions and a single specified “Run As” Unattended runner user should hopefully achieve this as long as that user does not have any other roles with “Run As” users specified.


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • Answer
  • December 7, 2023

Hi @JMarino & @Rob B .

 

Yes, an AARI Process can run on a specific BOT Runner. It is possible to configure an AARI process or a BOT that’s called within an AARI process to launch on a specific runner.

Here are the steps to accomplish this:

  1. Use the admin account and go to your Scheduler user role.
  2. Click on Edit.
  3. In the Bot section, give access to all Bots.
  4. In the Run-As section, select the runners in your Device pool.

 

Please note that bots executed through AARI Web are run on unattended Bot runners - using a device pool.

 

Please refer the below blog on the same.

Tech Talks: What is AARI? | Community (automationanywhere.com)

 

 
 

Forum|alt.badge.img+1
  • Cadet | Tier 2
  • June 5, 2024

What are the roles and licenses required to run the AARI process on same /local device


Forum|alt.badge.img
  • Cadet | Tier 2
  • October 31, 2025

The suggested steps are not helpful as we need to run some aari tasks on runner1 and other tasks on runner2. You can only choose 1 scheduler user, so I must choose a scheduler user that has both. Then in manage processes, I tried to set the user group and/or deployment tabs to use a custom resource of runner2 but this setting is ignored and the process tries to run on the other runner which has different resources and it fails.


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • November 3, 2025

The suggested steps are not helpful as we need to run some aari tasks on runner1 and other tasks on runner2. You can only choose 1 scheduler user, so I must choose a scheduler user that has both. Then in manage processes, I tried to set the user group and/or deployment tabs to use a custom resource of runner2 but this setting is ignored and the process tries to run on the other runner which has different resources and it fails.

You’re absolutely right that AARI currently doesn’t allow assigning different Bot Runners per task within the same process. The Manage Processes → Deployment tab settings are ignored because AARI uses the device pool linked to the scheduler user for execution.

The recommended approach is

  • Create separate AARI processes for tasks that need to run on different runners.
  • Assign each process to a scheduler user that has access to the correct device pool (e.g., Runner1 for Process A, Runner2 for Process B).
  • If you need to keep them logically grouped, you can manage this through AARI forms and orchestration, but execution will still be tied to the device pool.

Unfortunately, there’s no native way to override runner selection at the task level within a single AARI process. This is a current limitation of the platform.

I’d suggest raising this as an enhancement request on the Automation Anywhere Support Portal, as this feature would be very useful for resource-specific tasks.

Hope this clarifies why the setting is ignored and gives you a workable alternative.