- Getting started
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Resource Catalog Service
- Folders Context
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Storage Buckets
- Test Suite - Orchestrator
- Test Automation
- Testing Data Retention Policy
- Host administration
- Host Administration Portals
- Configuring System Email Notifications
- Managing System Administrators
- Configuring Host Security
- Host Audit Logs
- Customizing the Login Page
- Maintenance Mode
- Identity Server
- Organization administration
- Managing tags
- Audit Logs
- Overriding System Email Settings
- Other Configurations
Robot execution settings can be managed from Orchestrator for each robot, without having to connect to the robot machine each time.
Settings from either robot configuration or from UiPath Assistant are overwritten with the selected setting whenever robots connect to Orchestrator or when jobs are triggered from Orchestrator.
These settings stay the same regardless of robot and folder types.
The level at which the robot should log information.
The following options are available:
Allow Development logging
Enables you to choose whether or not you want to receive execution or debugging logs sent from Studio during development processes. By default, this is set to
Login To Console
Enables the Robot to connect to the console session of the machine where it is installed. Additionally, it indicates if you can connect multiple Robots to Orchestrator using multiple users (High-Density Robots) or not. By default, this is set to
Yes. To enable High-Density Robots, set the value to
If set to
No, the Unattended Robot creates an RDP session when executing a process.
The machine's display resolution width. This option is set to 0 by default, which means that it automatically retrieves and uses the detected resolution width. You can use a custom value, as long as it is supported by the workstation.
The machine's display resolution height. This option is set to 0 by default, which means that it automatically retrieves and uses the detected resolution height. You can use a custom value, as long as it is supported by the workstation.
The machine's display resolution depth. This option is set to 0 by default, which means that it automatically retrieves and uses the detected resolution depth. You can use a custom value, as long as it is supported by the workstation. Please note that Windows 10 does not support a Resolution Depth value other than 32.
Enhances text recognition. If is set to True, the Font Smoothing* option over RDP connections is turned on. This means that the target machine has ClearType turned on. By default, this is set to
Auto Download Processes
If enabled, available processes are automatically downloaded when the Robot agent starts. By default, this is set to
No. Take into account that a new session must be created for the resolution settings to take effect, so you need to log off
and then log back in again.