--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Start an unattended bot process # Start an unattended bot process in RPA Hub {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read 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](https://www.servicenow.com/docs/Fh5n_jyVL~kis5vxVwxTSQ "In RPA Hub, you can create a bot process configuration record and assign assets to associate it with a bot process. Or you can just save the bot process configuration record, however it won't be associated to a bot process. It remains orphaned."). 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 in RPA Hub](https://www.servicenow.com/docs/1SYpQgsolYA0s6xdTr1KNg#bot-process-form "Use the Bot Process form to associate it to the bot process configuration and populate the remaining fields required for a bot process."). If the External Credential check box is selected in a robot credential record, then ensure that the associated external credential vault record is active. For more information, see [Create a robot credential in RPA Hub](https://www.servicenow.com/docs/oKeoN0Q11ge6srmW7n8aYQ "Create a robot credential so that the unattended robot can log in to a Windows machine and perform the automation."). 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. {#start-bot-process__ul_e25_d4q_5xb} Note: When a bot process is either in the In Maintenance or Build life-cycle stage status and is using a robot pool, new robots are not deployed for dynamic allocation. Dynamic allocation in the robot pool is only activated for published bot processes. Only robots with an assigned credential group 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](https://www.servicenow.com/docs/3veXXzhhLruKukiVKYls7Q "Run an unattended robot to execute the unattended automations that are triggered either by a schedule, API, or manually."). Another way to start an unattended bot process is via triggering the Start Process Action in Workflow Studio. For more information, see [Workflow Studio actions and subflow in RPA Hub](https://www.servicenow.com/docs/FX0I6PkBXL8cOAh00m_fwQ "Two-way integration of actions and subflows in Workflow Studio and RPA Hub for a seamless robot execution."). ## Procedure 1. Navigate to AllRobotic Process AutomationRPA 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. The robots that are in the In Maintenance life-cycle stage status are not displayed in the list. 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\\\\\AppData\\Local * For user plugins, you can allow list the user plugins folder in the path \\\UserPlugins\\\ * For script connectors, you can allow list the Dependencies folder in the path \\\Dependencies {#start-bot-process__ul_zgk_mbg_t1c} **Related tasks** * [Edit a bot process in RPA Hub](https://www.servicenow.com/docs/R3yHpp2AAsnbWMrHytRPJQ "Edit an existing bot process in RPA Hub to modify a few details.") * [Stop an unattended bot process in RPA Hub](https://www.servicenow.com/docs/urCbR5d8TpabdgI7W6Uvvg "Stop the unattended bot process to abort the automation by the selected robot. If robot pool is enabled for a particular bot process, then the execution is stopped for all the robots of the robot pool.") * [Launch in Studio from RPA Hub](https://www.servicenow.com/docs/HXdB9J6O5V~hkknms0HfFw "Review, edit, and debug automations by opening the associated package version of the bot process in the RPA Desktop Design Studio.") * [Publish a bot process in RPA Hub](https://www.servicenow.com/docs/1bj72E5mlTi81g62f4wjNA "Publish a bot process so that you can get it ready to execute a process.") * [Retire a bot process in RPA Hub](https://www.servicenow.com/docs/YiOlONO0KwdVVX~WBmZOiw "Retire a bot process to turn it off. It's one of the life-cycle stages of a bot process. After you retire a bot process, you can't use it anymore.") *[\>]: and then