- 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
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting

Orchestrator user guide
Automation Cloud™ Robots - Serverless
Feature |
Testing - consumed amount 1 |
Production - consumed amount |
Details |
---|---|---|---|
Automation Cloud™ Robots - Serverless |
X RUs / minute that a job runs
|
X RUs / minute that a job runs
|
Cost: For every minute that a job runs,
X RUs are consumed from the tenant's available RUs for the year. The value of X depends on the machine size.
Consumption: The RUs are deducted from either a user's own RU pool (if granted by their license for the execution scenario) or from the tenant's available RUs. As an exception, after the user RU pool is depleted, user-run automations may consume RUs from the tenant pool, if available. The RUs are deducted after the job completes. Reserved RUs: For Serverless, RUs are not reserved, so the tenant pool must include sufficient available RUs to run jobs. |
1 You must be on the Enterprise,Pro, or Pro Trial licensing plan to use this feature.