Start an unattended bot process in RPA Hub

Start an unattended bot process in the specified robot machine to execute the automation by the selected robot.

Before you begin

Associate a package and a package version to the bot process. For more information, see Configuring a bot process record in RPA Hub.

Verify that the life cycle stage status of the bot process is either in Published, In Maintenance, or Build. For more information, see Bot Process form.

Role required: sn_rpa_fdn.rpa_developer, sn_rpa_fdn.rpa_support_user, sn_rpa_fdn.rpa_business_user, or sn_rpa_fdn.rpa_admin

About this task

If robot pool is enabled, after you select the Start Process button, a certain number of robots from the assigned robot pool execute the bot process based on the following conditions:
  • Based on the value selected in the Allocation Type field on the Bot Process form.
  • Based on the pending work items and average handling time of previous successfully completed work items, calculate the number of robots needed.
  • Minimum value of calculated robots is 1.
  • Maximum value of calculated robots is equal to the number of robots in the pool.

Only robots with an assigned credential set and in the Available and Busy states are displayed here to facilitate process job queuing. A job queue contains processes that are executed in a defined order.​​

You can also run an unattended automation using the Unattended Robot. For more information, see Run an automation using Unattended Robot.

Another way to start an unattended bot process is via triggering the Start Process Action in Flow Designer. For more information, see RPA actions and subflow.

Procedure

  1. Navigate to All > Robotic Process Automation > RPA Hub Workspace.
  2. Select the list icon (List icon.).
  3. On the Lists tab, under Build, select Bot Process.
  4. Open the bot process to execute the unattended automation.
  5. In the form header, select Start Process.
  6. Select the robot that is assigned to the current bot process that you want to start.
  7. Select Start Process.
    Your organisation’s security policy may flag or prevent the automation from executing. To avoid that, consider allow listing the folders that store the binaries, user plugins, and script connectors on your computer. For example,
    • For binaries, you can allow list the ServiceNowRPA folder in the path Users\<username>\AppData\Local
    • For user plugins, you can allow list the user plugins folder in the path <project folder name>\UserPlugins\<User plugin name>
    • For script connectors, you can allow list the Dependencies folder in the path <project folder name>\Dependencies