- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read Only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Audit
- Settings
- Cloud robots
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Troubleshooting
Automation Cloud™ Robots - Serverless
This page explains what Serverless Automation Cloud Robots are and how to set them up.
Serverless Automation Cloud robots make it easy to run background automation without worrying about the necessary infrastructure. They provide you with complete freedom from provisioning, managing, maintaining, and scaling any underlying infrastructure. UiPath handles all the work behind the scenes so you don't have to deal with containers, virtual machines, or physical servers.
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.
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 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.
On the Machines page, a success message is displayed along the top and you can see your new template in the list.
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.
Orchestrator allows launching unattended jobs manually from the Jobs page or automatically triggered in a pre-planned manner via triggers.
- Go to the folder that contains the processes, by selecting it in the sidebar menu.
- In the context of the selected folder, go to Automations > Jobs. The Jobs page is displayed.
- Click Start to start a new job.
- From the Runtime license drop-down, select Cloud - Serverless or Cloud - Serverless Testing.
- Click Start. A Command sent message is displayed and you can see the job in the list.
To run processes using serverless robots, you must have the required amount of RUs (robot units) available for the tenant in which the process needs to run.
The amount of RUs that are consumed depends on:
- the type of environment - test environments have lower RU consumption than production environments;
- the size of the serverless robot machine;
- the number of minutes it takes to execute a job.
The following machine sizes are available:
Machine size |
Testing RUs/minute 1 |
Production RUs/minute |
---|---|---|
Small (1GB) |
0.5 |
1 |
Standard (2GB) |
1 |
2 |
Medium (4GB) |
2 |
4 |
Large (10 GB) |
5 |
10 |
1 You must be on the Enterprise, Pro, or Pro Trial licensing plan to use this feature.
Because each process has particular needs, you set the machine size in the configuration of a process.
For any cross-platform process, the Cloud Robot - Serverless list is available on the Additional Settings tab when creating or editing a 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.
All your cross-platform processes have the Cloud Robot - Serverless option set to Automatic by default. This setting selects the appropriate machine size for running the process using serverless robots.
The amount of robot units consumed to run the process is based on the machine size and the number of minutes it takes to run.
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 OR Process depends on the UiPath Document Understanding activities |
Standard |
3 |
Other unattended process |
Small |
When using client credentials to connect your serverless robots to Orchestrator, the serverless machine template generates a client ID and client secret pair that authorizes the connection between that host machine and Orchestrator. If you feel that the secret key has been compromised, you can regenerate the client secret:
You can edit the VPN setup for a Cloud Robot - Serverless template at any time, or disconnect the template from VPN.
To find out how you can request a free trial for Serverless Automation Cloud Robots, check Requesting a service trial page.
While a job is in progress, you can access the live stream of the robot running the automation. If troubleshooting or debugging is needed, you can take control of the execution using your own mouse and keyboard, without pausing the automation.
The live streaming and remote control features are available for Automation Cloud Robots (both Serverless and VM), Elastic Robots, and Windows Robots version 2023.4+.
To enable live streaming and remote control, see Enabling the features.
Serverless robots can only run background, cross-platform automations, so make sure the process you are trying to execute was designed as a background, cross-platform process in Studio.
Yes. Make sure the serverless machine template is added to the folder or personal workspace where the process resides.
With a Community account, you can run up to three jobs concurrently per tenant. With an Enterprise account, you can run up to fifty jobs concurrently per tenant.
You are only limited by the amount of available robot units (RUs) for the tenant.
The number of jobs you can run depends on whether serverless robots run in a test environment or a production environment, how long your jobs take to run, and the size of the machine running the job. For example, in a production environment, a 1-minute job run on a Medium size robot (4 GB) consumes 4 RUs.
For more information, see Robot units: Consumption.
All machines are created and hosted in the tenant region.
Organization administrators can see what the region is for a tenant in Tenant Settings (Admin > Tenants).
All activities that are available for cross-platform projects can be run with serverless robots. This includes but is not limited to:
- Browser-based automations using the Chromium browser
- Integration Service activities
- API-based automations (Including HTTPS API calls that require using your own SSL certificates for authentication by downloading the certificates to the /tmp/certs filepath)
- Database activities that require Oracle, MySql, MSSQL & PostgreSQL ODBC drivers.
Browser-based automations using the Chromium browser may require client certificate authentication.
register-client-cert -d domain -c path/to/certificate.p12 [-p password]
register-client-cert -d domain -c path/to/certificate.p12 [-p password]
-
-d - is the domain to access
-
-c - is the path to the client certificate
-
-p - is the certificate password
var process = System.Diagnostics.Process.Start("register-client-cert", "-d client.badssl.com -c /tmp/home/badssl.com-client.p12 -p badssl.com"); process.WaitForExit(10000);
var process = System.Diagnostics.Process.Start("register-client-cert", "-d client.badssl.com -c /tmp/home/badssl.com-client.p12 -p badssl.com"); process.WaitForExit(10000);
We are unable to provide the list or range of IP addresses used in Serverless as they are dynamic.
- Executing Unattended Automations With Serverless Robots
- Step 1. Enabling Unattended Automation on an Account
- Step 2. Adding Serverless Robots to Your Tenant
- Step 3. Giving Access to Folder Resources
- Step 4. Executing Unattended Automations: Manually
- Step 4. Executing Unattended Automations: Automatically Triggered
- Machine Sizes and Costs
- Choosing the Machine Size
- Automatic Machine Size Selection
- Regenerating Client Secrets
- Managing VPN Settings
- Disconnecting a Template From VPN
- Changing the Address Space
- Asking for a trial
- Live streaming and remote control
- Frequently Asked Questions
- Why can't I see serverless robots machine templates when starting a job?
- Can I debug processes remotely from Studio on serverless robots?
- How many jobs can I run in parallel on serverless robots?
- How many jobs can I run using serverless robots?
- In which region are the serverless machines hosted?
- What activities and projects can serverless robots run?
- How can I authenticate Chromium-based automations using my client certificate?
- What are the list of IP addresses used for serverless robots?
- Where can I find data downloaded through activities?