Executing Unattended Automations With Serverless Robots

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 and process compatibility.
• 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.

1. Go to Tenant > Manage access. A window is displayed listing all accounts in that tenant.
2. Click More Actions > Edit to enable unattended automation for an existing account or Assign Roles > User to reference a user account from Automation Cloud.
3. On the Robot setup tab (step 2), enable the toggle for the Unattended Robot.
   
   

   

   
   
4. Click 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 serverless robots.
   • 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, click 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.

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

6. (Optional) To use a previously configuredVPN gateway , go to the VPN Setup 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.
7. Click 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, click 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.

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

7. (Optional) To use a previously configuredVPN gateway , go to the VPN Setup 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. Click 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.

  
  

  

  
  

• Adding the user/robot account to a folder.

  
  

  

  
  

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. Click Start to start a new job.
4. From the Runtime license drop-down, select Cloud - Serverless or Cloud - Serverless Testing.
5. Click 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. Click Add a new trigger to configure the mechanism for launching the jobs via triggers.
4. Configure the necessary fields.
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. Click 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.