---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Execution priority of bot processes

# Execution priority of bot processes in RPA Hub {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Execution Priority of Bot Processes in RPA Hub

This guide explains how to prioritize bot processes in RPA Hub, helping you manage automation effectively and prevent conflicts when multiple processes are scheduled on the same robot.
Understanding this prioritization is crucial for ensuring efficient execution and resource allocation.
Show full answer Show less  

## Key Features

* **Execution Logic:** When multiple bot processes are scheduled, they are organized by robots and Windows user credentials. The process with the lowest priority number within each group executes first.
* **Scheduled Triggers:**
  * For different Windows credentials, processes are grouped by robot, and the lowest priority number executes.
  * For the same Windows credentials, processes are first grouped by robot, but conflicts are resolved by executing the lowest priority from the grouped credentials.
* **Manual Triggers:**
  * When triggered manually with the same credentials, one robot executes the process while the other is skipped.
  * With different credentials, both robots execute the process simultaneously.

## Key Outcomes

By understanding and applying these prioritization rules, you can effectively manage bot processes in RPA Hub, reducing the risk of automation conflicts and ensuring that the most critical tasks are executed efficiently. This leads to improved productivity and streamlined operations within your automation framework.  
Learn how to prioritize bot processes efficiently and avoid triggering multiple automations on the same robot. The bot processes are organized by both robots and Windows user credentials.

## Scheduled trigger {#bot-process-prioritization-order-rpa-hub__section_kff_fvm_xdc}

When multiple bot processes are scheduled to run at the same time, consider the following scenarios to understand how bot process execution is prioritized based on order number and Windows credentials.
Figure 1. Scenario 1: Robots with different Windows credentials

The following bot processes use robots 1 and 2 with different priority orders and the robots use different credentials to login to a Windows machine.

* Bot process 1
  * Robot: Robot 1
  * Order: 2
  * Windows credential: SN\\User 1
  {#bot-process-prioritization-order-rpa-hub__ul_lyr_1vf_tdc}
* Bot process 2
  * Robot: Robot 1
  * Order: 3
  * Windows credential: SN\\User 2
  {#bot-process-prioritization-order-rpa-hub__ul_myn_fvf_tdc}
* Bot process 3
  * Robot: Robot 2
  * Order: 4
  * Windows credential: SN\\User 3
  {#bot-process-prioritization-order-rpa-hub__ul_c11_hvf_tdc}
* Bot process 4
  * Robot: Robot 2
  * Order: 1
  * Windows credential: SN\\User 4
  {#bot-process-prioritization-order-rpa-hub__ul_egd_3vf_tdc}

{#bot-process-prioritization-order-rpa-hub__ul_ssb_prf_tdc}  
When all bot processes are scheduled to start simultaneously, execution is determined based on the following logic:

1. Bot processes are grouped by the robot.
2. Within each group, the bot process with the lowest priority number is executed.
{#bot-process-prioritization-order-rpa-hub__ol_cwp_nvf_tdc}  
Execution results:

* Robot 1: Bot Process 1 (priority 2) executes; Bot Process 2 (priority 3) is skipped.
* Robot 2: Bot Process 4 (priority 1) executes; Bot Process 3 (priority 4) is skipped.
{#bot-process-prioritization-order-rpa-hub__ul_ul4_rvf_tdc} Figure 2. Scenario 2: Robots with the same Windows credential

The following bot processes use high-density robots 1 and 2 with different priority orders and use same credentials to login to a Windows machine.

* Bot process 1
  * Robot: Robot 1
  * Order: 2
  * Windows credential: SN\\User 1
  {#bot-process-prioritization-order-rpa-hub__ul_lsc_gwf_tdc}
* Bot process 2
  * Robot: Robot 1
  * Order: 3
  * Windows credential: SN\\User 1
  {#bot-process-prioritization-order-rpa-hub__ul_msc_gwf_tdc}
* Bot process 3
  * Robot: Robot 2
  * Order: 4
  * Windows credential: SN\\User 1
  {#bot-process-prioritization-order-rpa-hub__ul_nsc_gwf_tdc}
* Bot process 4
  * Robot: Robot 2
  * Order: 1
  * Windows credential: SN\\User 1
  {#bot-process-prioritization-order-rpa-hub__ul_osc_gwf_tdc}

{#bot-process-prioritization-order-rpa-hub__ul_ksc_gwf_tdc}  
When all bot processes are scheduled to start simultaneously, priority is determined based on the following logic:

1. Bot processes are first grouped by the robot.
2. Within each group, the bot process with the lowest priority number is selected.
{#bot-process-prioritization-order-rpa-hub__ol_ptc_gwf_tdc}  
Intermediate priority results:

* Robot 1: Bot Process 1 (priority 2) is selected over Bot Process 2 (priority 3).
* Robot 2: Bot Process 4 (priority 1) is selected over Bot Process 3 (priority 4).
{#bot-process-prioritization-order-rpa-hub__ul_qtc_gwf_tdc}

However, Bot Process 1 and Bot Process 4 cannot be launched in the same Windows session simultaneously due to shared credentials (SN\\User1). To resolve this conflict, bot processes are grouped by Windows credentials, and the process with the lowest priority number is executed:  
Final execution results:

* SN\\User1: Bot Process 4 (priority 1) executes.
* SN\\User1: Bot Process 1 (priority 2) is skipped.
{#bot-process-prioritization-order-rpa-hub__ul_ttx_pwf_tdc}

## Manual trigger {#bot-process-prioritization-order-rpa-hub__section_rrg_jvm_xdc}

When a bot process with multiple high-density robots is triggered using the Start Process button, consider the following scenarios to understand how bot process execution is prioritized for a robot.
Figure 3. Bot process prioritization for different high-density robots

Scenario 1: Robots with the same Windows credentials
:   The Bot process 1 uses high-density robots 1 and 2 with the same credentials to login to a Windows machine. When the Start Process button is clicked on the Bot process 1 for Robot 1 and Robot 2, any one robot is picked randomly to execute the bot process. The
    process job with the Skipped status is created for the other robot.

Scenario 2: Robots with different Windows credentials
:   The Bot process 1 uses high-density robots 1 and 2 with different credentials to login to a Windows machine. When the Start Process button is clicked on the Bot process 1 for Robot 1 and Robot 2, both the robots execute the bot process simultaneously.