Run a bot
Feedback
- Updated: 2024/03/25
Run a bot
You can run a bot to test an automated process.
Procedure
- Log in to the Control Room.
-
On the left pane in the public workspace, click
Automation.
A list of available bots and forms is displayed.
-
Select the bot to run.
Hover over the actions menu (vertical ellipses) located to the right of the bot name and click Run Task Bot.If an optional Bot Agent update for your device is available, the following message that Bot Agent has an update is displayed one time per user session or when you log out and log in to the Control Room.
- To download and update the Bot Agent to the latest version on your device, use the Click here link.
- To opt out of the update and continue with the existing Bot Agent version on your device, click Continue without update.
-
Select the version of the bot to run.
- Latest version: To select the latest version of the bot, click the Latest version tab.
- Labeled version: To select the labeled version of the bot, click the Production version tab.
By default, the latest version of the bot is selected. If the production label option is selected for the parent bot, the corresponding dependent bots with the production label are also automatically selected. If any of the dependent bots do not have the production label applied, the latest version of the bot is selected. - Click the right arrow (→) to add your selection.
-
Select the Bot Runner users from the list of
Available bot runners in the Run
as tab.
The list of Bot Runner users that you have access to are displayed.
- Click the right arrow (→) to add your selection.
-
Select the pool from the list of Available device pools
in the Device pools tab.
The list of device pools for which you have a consumer role are displayed. Select the device pool only if any of the selected Bot Runner users do not have a bot running (default) device.
- Click the right arrow (→) to add your selection.
- Optional:
Use the Resiliency settings tab to change the following
options:
- In the Pop-up handling field, clear the
Ignore unexpected pop-ups check box if you do not
want to avoid any pop-ups during the bot runtime.
This option is enabled by default. If you disable this option, any unexpected pop-ups that occur during the bot run can impact the automation or delay the runtime.
- In the Bot execution
recording field, change the following options:
- Store bot execution recording: Clear this check box if you want to prevent the bot execution from being recorded.
- Recording preferences: If you have opted to
record automations, you can further select one of the following options
for recording bot executions:
- Only failed executions: Recording will be stored only when the automation execution fails.
- All bot executions: Recording is stored irrespective of whether the execution is successful or failed.
Note: Functionality to record automation execution requires the Enterprise Platform license. Contact your Automation Anywhere account representative for more information about this license.
- In the Pop-up handling field, clear the
Ignore unexpected pop-ups check box if you do not
want to avoid any pop-ups during the bot runtime.
- Optional:
Use the General tab to change the default settings for the
following options:
- Name: Edit or rename the bot.
- Automation priority: Click the drop-down menu to set
the automation priority.
While Medium is the default automation priority, you can change it so that automations are processed for deployment accordingly.
- Clear the
Hide bot run window check box.
This option is enabled by default and hides the bot run progress window from view. If you disable this functionality, progress window is displayed when the bot starts.
-
Click Run bot now.
Note: If you have not set the device credentials from the My settings page, you are prompted to provide the device credentials to run the bot.
If you encounter issues in running a bot, refer to the following
articles:
- Automation 360 - Unable to download the bot or the dependencies to the device; Error code: download.error (A-People login required).
- There is already an existing deployment in-progress for this user session (A-People login required).
- BOT stuck in In Progress Stage and not able to move it to history" or "BOT stuck in Pending execution Stage and not able to move it to history" on Automation 360 CLOUD and On-Prem environments