# Executing Unattended Automations With Automation Suite Robots

> Execute unattended automations using Automation Suite Robots by enabling unattended capabilities on the target account.

:::note
Feature availability depends on the cloud offering that you use. For details, refer to the [Feature availability page](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/orchestrator-feature-availability#orchestrator-feature-availability).

If you are using Automation Cloud, Test Cloud, Automation Cloud Public Sector, or Test Cloud Public Sector, use Automation Cloud Robots.
:::

## 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.

1. Go to **Tenant** > **Manage access**. 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 Roles > User** to reference a user account from Automation Suite.
3. On the **Robot setup** tab (step 2), enable the toggle for the **Unattended Robot**.

Figure 1. Unattended Robot toggle button

![Unattended Robot toggle button](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-unattended-robot-toggle-button-226771-f2bc90e2-2cade8be.webp)

4. Select **Update** to update an existing account or **Create** to add a new one.
:::note
* The **Machine login credentials** and **Run only one job at a time** settings do not apply to Automation Suite robots.
* The account which is used for execution and the roles assigned to the account allow for a certain level of access to resources.
To ensure successful execution of the process, make sure the account has the necessary roles to perform the operations required by the processes they will execute.
:::

## Step 2. Adding Automation Suite Robots to Your Tenant

To enable execution you need to create a machine template of the type **Automation Suite Robot** - a type of machine template used to add the Automation Suite robots capability to your Orchestrator tenant.

1. Go to **Tenant > Machines**.
2. In the top right, Select **Add Machine** and select **Automation Suite Robot**.

The **Machine template** page opens.

Figure 2. Machine template

![Screenshot of the Machine template page](https://docs.uipath.com/orchestrator/automation-suite/2.2510/user-guide/managing-machines)

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 runtime license requirements and the runtime type to use when running jobs are shown on the right.
:::

5. On the right, in the **Production (Unattended)** or **Testing** field, Enter the number of runtimes you want to allocate to this template.

  The number of runtimes that you allocate is the umber of processes that can run at the same time on Automation Suite robot. For example, allocating three runtimes means that up to three processes can run at the same time.

  The allocated runtimes are subtracted from the number of runtimes available for the tenant after you create the template. The runtimes are never released as long as the template exists, even if they are not in use.

  When a machine template is used exclusively for agent execution, no license assignment is required. Running Agents on Automation Suite robot will consume [units](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/coded-agents-licensing).

6. 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 **Automation Suite 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 Automation Suite Robot machine template to a folder](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/assigning-machine-objects-to-folders).

Figure 3. Managing machines in a folder

  ![Screenshot of the Manage machines in a 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 or robot account to a folder](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-folders).

Figure 4. Assigning accounts

  ![Screenshot of the Assign Account/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 1 hour. Jobs that take longer are terminated when they reach 1 hour of execution time. Optimize your automation projects or split them into multiple workflows to avoid reaching the 1 hour 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 **Production (Unattended)** or **Testing**.
5. Select **Start**.

A **Command sent** message is displayed and you can see the job in the list.

## Step 5. 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 **Production (Unattended)** or **Testing**.
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.

## Machine Sizes and Costs

To run processes using serverless robots, you must have:

* the required number of **Production (Unattended)** or **Testing** runtimes available for the tenant in which the process needs to run
* adequate hardware to support the required number of executions.

### Supported runtimes

You can choose between **Production (Unattended)** or **Testing** runtimes to run jobs. The following table describes each option.

| License type | Runtime behavior |
| --- | --- |
| Production (Unattended) | You can use this runtime in production to run unattended processes. |
| Testing | You can use this runtime to run test sets and test cases as well as unattended processes. |

### Choosing the machine size

Because each process has particular needs, you set the machine size in the configuration of a process.

For any cross-platform process, the **Automation Suite machine size** list is available on the **Additional Settings** tab when creating or editing a process. Use this list to choose the machine size you want to use for each process.

The option is available for all cross-platform processes, which are candidates for being run using serverless robots, but the option has no effect unless it is executed by a serverless robot.

### Automatic machine size selection

All your cross-platform processes have the **Automation Suite machine size** option set to **Automatic** by default. This setting selects the appropriate machine size for running the process using serverless robots.

When automatically choosing the size, the criteria listed in the below table are evaluated in order. As soon as one criterion is satisfied, the corresponding machine size is chosen and the remaining criteria are not evaluated.

| Order | Criterion | Machine size |
| --- | --- | --- |
| 1 | Remote debugging job | Medium |
| 2 | Process depends on [UI Automation](https://docs.uipath.com/studio/docs/ui-automation)  OR  Process depends on the [UiPath Document Understanding activities](https://docs.uipath.com/document-understanding/docs/activities-packages) | Standard |
| 3 | Other unattended process | Small |