# Executing unattended automations with Serverless robots > Execute unattended automations using serverless robots with a background cross-platform process published to Orchestrator. :::note **Prerequisites** * A background, cross-platform automation project that has been published to Orchestrator and added to your folders. Learn more about [background and foreground processes](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-processes#background-vs-foreground-processes) and [process compatibility](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-processes#process-compatibility). * [Robot units](https://docs.uipath.com/overview/other/latest/overview/service-licensing#robot-units) available for the tenant. ::: ## Step 1. Enabling unattended automation on an account To run unattended automations with a specific account you need to first enable unattended automation on that account. You can skip this step if you are using robot accounts since they come with unattended automation capabilities by default. To run unattended automations, we recommend using a Robot account. 1. Go to **Tenant** > **Manage access** > **Access Rules** > **Robot accounts**. A window is displayed listing all accounts in that tenant. 2. Select **More Actions** > **Edit** to enable unattended automation for an existing account or **Assign robot account** to reference a Robot account from Automation Cloud. 3. On the **Robot setup** tab (step 2), enable the toggle for the **Unattended Robot**. Figure 1. Enabling unattended robots ![Screenshot of the Assign access rules to a Robot account page](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-assign-access-rules-to-a-robot-account-page-602009-575c2a11-7167e582.webp) 4. Select **Update** to update an existing account or **Assign** to add a new one. :::note * The **Custom Windows credentials** and **Run only one job at a time** settings do not apply to serverless robots. The behavior varies depending on how the account is assigned and whether credentials are configured: | Assignment type | Custom Credentials | Behavior | |---|---|---| | Group | Configured | The job fails. Orchestrator switches to an unattended robot lookup bound to those credentials, but group-resolved users are not found in the folder context. | | Group | None | The job succeeds. Orchestrator falls back to an attended/RunAsMe lookup, which correctly handles group membership. | | Direct | Configured | The job succeeds. The user is found directly, but the job runs as `username@domain.com-attended` due to the serverless runtime. | * The account used for execution and its association with roles allow for a certain level of access to resources. To ensure successful execution of the process, make sure the account has the necessary permissions to perform the operations required by the processes they will execute. ::: ## Step 2. Adding Serverless robots to your tenant To enable execution you need to create a serverless robot machine - a type of machine template used to add the serverless robots capability to your Orchestrator tenant. 1. Go to **Tenant > Machines**. 2. In the top right, Select **Add Machine** and select **Cloud Robot - Serverless**. The **Machine template** page opens on the **Machine** step. 3. Fill in the **Name** field and, optionally, fill in the **Description** field for the machine template. 4. Optionally, under **Tags**, if you want to keep track of this machine object together with other resources, define tags. For detailed instructions, see [Adding tags to machine objects](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-machines). :::note Details about the robot unit requirements and the runtime type to use when running jobs are shown on the right. By default, the optimal machine size is selected automatically for each process. You can choose the size from the [Advanced Settings](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-processes) tab for a process. ::: 5. (Optional) For tenants with the account-machine mappings setting enabled, go to the **Account-machine mappings** page. There, you can set up specific accounts to use the machine. For details, see [Configuring account-machine mappings](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configuring-account-machine-mappings#configuring-account-machine-mappings). 6. (Optional) To enable [Static IP](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/outbound-ip-ranges#availability), go to the **Network Configuration** page. 1. Check the **Enable Static IP** box. You can consult the IP ranges in the linked page. :::note The **Enable Static IP** option appears only in regions where static IP is available. It is not shown in South Korea, Switzerland, or European Union — delayed update (GxP). ::: 7. (Optional) To use a previously configured [VPN gateway](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-vpn-settings#managing-vpn-settings) , go to the **Network Configuration** page. 1. Switch on the **Enable VPN Integration** toggle. The VPN settings are displayed. 2. In the **Address space** field, add the reserved IP addresses you received from your network administrator, in CIDR notation with a mask of `/16` or greater. :::note If the **Address space** field is not displayed, check that the VPN gateway for the tenant is successfully deployed. ::: 8. Select **Provision**. On the **Machines** page, a success message is displayed along the top and you can see your new template in the list. ### Creating a Serverless template To enable execution you need to create a serverless robot machine - a type of machine template used to add the serverless robots capability to your Orchestrator tenant. 1. Go to **Tenant > Machines**. 2. In the top right, Select **Add Machine** and select **Cloud Robot - Serverless**. The **Machine template** page opens on the **Machine** step. 3. Fill in the **Name** field and, optionally, fill in the **Description** field for the machine template. 4. Optionally, under **Tags**, if you want to keep track of this machine object together with other resources, define tags. For detailed instructions, see [Adding tags to machine objects](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-machines). :::note Details about the robot unit requirements and the runtime type to use when running jobs are shown on the right. By default, the optimal machine size is selected automatically for each process. You can choose the size from the [Advanced Settings](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-processes) tab for a process. ::: 5. Under **Runtime details**: 1. Enter the number of **Production (Unattended)** and/or **Testing** runtimes you need to execute an unattended or a non-production automation. 6. (Optional) For tenants with the account-machine mappings setting enabled, go to the **Account-machine mappings** page. There, you can set up specific accounts to use the machine. For details, see [Configuring account-machine mappings](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configuring-account-machine-mappings#configuring-account-machine-mappings). 7. (Optional) To enable [Static IP](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/outbound-ip-ranges#availability), go to the **Network Configuration** page. 1. Check the **Enable Static IP** box. You can consult the IP ranges in the linked page. :::note The **Enable Static IP** option appears only in regions where static IP is available. It is not shown in South Korea, Switzerland, or European Union — delayed update (GxP). ::: 8. Select **Provision**. On the **Machines** page, a success message is displayed along the top and you can see your new template in the list. ## Step 3. Giving access to folder resources In order to run unattended automations, both the account and the serverless robot machine template must have access to the process to be executed. To do this, you must add the account and machine object previously configured (steps 1 and 2) to the folder that contains the process. * [Adding the serverless robot machine template to a folder](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/assigning-machine-objects-to-folders). Figure 2. Managing machines in folder ![Screenshot of the ManageMachines in Folder button](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-manage-machines-in-a-folder-button-229309-0dae422f-063880cc.webp) * [Adding the user/robot account to a folder](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-folders). Figure 3. Assigning accounts ![Screenshot of the Assign Accounts/Group button](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-assign-account-group-button-227443-3b8f02be-1ec23c43.webp) ## Step 4. Executing unattended automations: manually Orchestrator allows launching unattended jobs manually from the **Jobs** page or automatically triggered in a pre-planned manner via triggers. :::important Each job is limited to 15 minutes. Jobs that take longer are terminated when they reach 15 minutes of execution time. Optimize your automation projects or split them into multiple workflows to avoid reaching the 15-minute limit. ::: 1. Go to the folder that contains the processes, by selecting it in the sidebar menu. 2. In the context of the selected folder, go to **Automations** > **Jobs**. The **Jobs** page is displayed. 3. Select **Start** to start a new job. 4. From the **Runtime license** drop-down, select **Cloud - Serverless** or **Cloud - Serverless Testing**. 5. Select **Start**. A **Command sent** message is displayed and you can see the job in the list. ## Step 4. Executing unattended automations: automatically triggered 1. Go to the folder that contains the processes, by choosing it from the sidebar menu. 2. In the context of the selected folder, go to **Automations** > **Triggers**. The **Triggers** page is displayed. 3. Select **Add a new trigger** to configure the mechanism for launching the jobs via triggers. 4. Configure the [necessary fields](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-triggers). 5. On the **Runtime license** drop-down, select **Cloud - Serverless** or **Cloud - Serverless Testing**. :::note If you are on the **Community** licensing plan and you select the serverless runtime, the **Set execution-based trigger disabling** option is automatically enabled, with the following default values (the fields are read-only): * **Disable when consecutive job execution fail count** is set to 10. * **Grace period on disabling the trigger (days)** is set to 0. ::: 6. Select **Add**. A **Save successful** message is displayed and you can see the trigger in the list. A job is launched according to your configuration. All jobs and their statuses are listed on the **Jobs** page.