orchestrator

2023.4

false

Getting started
- Introduction
- User options
- Logging in to Orchestrator
- Resetting your password
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
  - Useful concepts in unattended automation
  - How is unattended automation performed
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
  - 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
  - SmartCard Authentication
- Folders
  - Managing Folders
  - Classic Folders Vs Modern Folders
  - Migrating From Classic to Modern Folders
  - Administration of Modern Folders
  - Personal Workspaces
  - Managing Personal Workspaces
- Monitoring
  - Unattended sessions
  - User sessions
  - License
- Managing Access and Automation Capabilities
  - Assigning Roles
  - Managing Roles
  - Default roles
  - Configuring access for accounts
  - Enabling personal automations
  - Enabling unattended automations
  - Configuring robot accounts to run unattended automations
- Machines
  - Managing Machines
  - Assigning Machine Objects to Folders
  - Configuring Account-machine Mappings
  - EDR Protection Status
- Packages
  - Managing Packages
  - About Libraries
  - Managing Libraries
- Audit
- Credential Stores
  - Managing credential stores
  - Integrating credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
  - Configuring Alerts
  - Alert Emails
  - Setting up Alert Emails
- Settings - Tenant Level
Resource Catalog Service
- About Resource Catalog Service
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Troubleshooting Jobs
Triggers
- About triggers
  - Time triggers
  - Queue triggers
- Managing triggers
  - Creating a Time Trigger
  - Creating a Queue Trigger
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Exporting usage data
Queues
- About Queues and Transactions
  - Queue Item Statuses
  - Business Exception Vs Application Exception
  - Studio Activities Used With Queues
  - Queue Item Retention Policy
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
Orchestrator testing
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
  - Managing Test Data Queues in Orchestrator
  - Managing Test Data Queues in Studio
  - Field Descriptions for the Test Data Queues Page
  - Test Data Queue Activities
- Testing Data Retention Policy
Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
  - Managing Robots
  - Robot Statuses
  - Setup Samples
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
  - Reconfiguring authentication after upgrade
  - Allowing or restricting basic authentication
  - Configuring SSO: SAML 2.0
    - ADFS Authentication
    - Google Authentication
    - Okta Authentication
    - PingOne Authentication
    - Custom Mapping
    - Self-signed Certificates
    - Private Key Certificates
  - Configuring SSO: Google
  - Configuring SSO: Microsoft Entra ID
  - Configuring the Active Directory Integration
    - Switching between Active Directory adapters
- Managing your host license
  - Allocating Licenses to Tenants
- Configuring system email notifications
- Configuring other host settings
  - Customizing the Login page
  - Session Policy
  - Orchestrator Host Settings
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- Managing organization administrators
- Managing organization settings
- Configuring organization authentication
  - Allowing or restricting basic authentication
  - Setting up the Azure AD integration
  - Configuring the SAML integration
- Configuring organization security
  - Session policy
  - Restricting access to a set of users
- About licensing
  - Activating your license
- Accounts and groups
  - Managing access
  - Managing accounts and groups
- Authorizing external applications
  - Managing external OAuth applications
  - Configuring fine-grained access for confidential apps
- Managing tags
- Overriding system email settings
  - Email setup
    - System emails are not sent - SslHandshakeException
- Audit logs
Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator user guide

DELIVERY:

Last updated Aug 26, 2025

Logging Levels

Logging Levels in UiPath

Logging Level	Default Logs	User-Defined Logs
Off	None	None
Critical	All messages logged with Critical level or higher.	All messages logged with Critical level or higher.
Error	All messages logged with Error level or higher.	All messages logged with Error level or higher.
Warning	All messages logged with Warning or higher.	All messages logged with Warning or higher.
Information	All messages logged with Information or higher.	All messages logged with Information or higher.
Trace	All messages logged with Trace level or higher.	All messages logged with Trace level or higher.
Verbose	All messages logged with Trace level and Workflow Tracking logs.	All messages logged with Trace level.

The Verbose level logs a message for both the activity start and end, plus the values of the variables and arguments that are used.

By default, the Verbose level includes:

Execution Started log entry - generated every time a process is started.
Execution Ended log entry - generated every time a process is finalized.
Transaction Started log entry - generated every time a transaction item is obtained by the robot from Orchestrator.
Transaction Ended log entry - generated every time the robot sets the transaction status to either Success or Failed.

Activity Information log entry - generated every time an activity is started,faulted or finished inside a workflow.

Note: The priority order of the log types is: Verbose < Trace < Information < Warning < Error < Critical < Off.

Log Level	Logged	Example / Comment	Log File	Output Panel	Orchestrator Log page
Verbose	Activities	`Trace {"message":{"DisplayName":"Message box","State":"Executing","Activity":"UiPath.Dialog.Activities.MessageBox","Arguments":{"Caption":"","Text":"String in message BOX	Yes	No	Yes
Verbose	Variables	`"Variables":{"NewTransaction":"False	Yes	No	Yes
Verbose	Arguments (properties)	`"Arguments":{"Caption":"","Text":"String in message BOX","ChosenButton":"Ok	Yes	No	Yes
Trace	Activities	`Trace {"message":{"DisplayName":"Main","State":"Executing","Activity":"System.Activities.DynamicActivity	Yes	No	Yes
Information	WriteLine Log Message	`Info {"message":"message from activity"` Note: Except messages logged with Trace level set in activity.	Yes	Yes	Yes
Warning	Warnings	`Warn {"message":"Warning from log message activity"`	Yes	Yes	Yes
Warning	Errors	`Error {"message":"Error from log message activity"`	Yes	Yes	Yes
Warning	Critical	Critical Errors	Yes	Yes	Yes
Error	Errors	`Error {"message":"Error from log message activity"`	Yes	Yes	Yes
Error	Critical Fatal	Critical Errors	Yes	Yes	Yes
Critical	Critical Fatal	Critical Errors	Yes	Yes	Yes
OFF	n/a	n/a	No	No	No

Log Message Types

There are several possible occurrences of log messages, depending on the event that is logged, as follows:

Default Logs

Generated by default when the execution of a project starts and ends, when a system error occurs and the execution stops, or when the logging settings are configured to log the execution of every activity.

Note: These logs have the Default value in the logType field.

The events logged by this category are:

Execution Start is generated every time a process is started. This is logged starting with the Information logging level.
Execution End is generated every time a process is finalized. This is logged starting with the Information logging level.
Transaction Start is generated every time a transaction within a process is started. This is logged starting with the Information logging level.
Transaction End is generated every time a transaction within a process is finalized. This is logged starting with the Information logging level.
Error Log is generated every time the execution encounters an error and stops. This is logged starting with the Error logging level.
Debugging Log is generated if the Robot Logging Setting is set to Verbose and contains, activity names, types, variable values, arguments etc. This is logged starting with the Trace logging level.

User-Defined Logs

Generated according to the process designed by the user in Studio, when using the Log Message activity or the Write Line activity.

Note: These logs have the User value in the logType field.

Log Fields

There are multiple types of log fields that can be found throughout the above log message types. These can be classified as follows:

Default Fields

These log fields are present in all execution type logs, such as SQL (if configured), Elasticsearch (if configured), and the default EventViewer Logs:

Message - The log message.
Level - Defines the log severity.
Timestamp - The exact date and time the action was performed.
FileName - The name of the .xaml file being executed.
jobId - The key of the job running the process.
processName - The name of the process that triggered the logging.
processVersion - The version number of the process.
windowsIdentity - The name of the user that performed the action that was logged.
robotName - The name of the robot (as defined in Orchestrator).

In an environment with multiple Robots on a machine which are connected to Orchestrator, the Event Viewer logs might display the following message: “Current user did not login to the application!". This occurs only if you remove a Robot that still had logs to send to Orchestrator.

Note: The processName and processVersion fields do not appear in logs if the process is run locally, without being connected to Orchestrator.

Type-specific Fields

These logs are present depending on the log type:

Execution End

totalExecutionTimeInSeconds
totalExecutionTime

Transaction Start

queueName
transactionID
transactionState

Transaction End

queueName
transactionID
transactionState
transactionStatus
transactionExecutionTime
processingExceptionType
processingExceptionReason
queueItemReviewStatus
queueItemPriority

Debugging Log

activityInfo, which is a JSON message with the following fields:
- DisplayName
- State (Faulted, Closed, Executing)
- Activity
- Variables
- Arguments
  
  Note: Only totalExecutionTimeInSeconds, totalExecutionTime and queueName are always present in the log messages. Variables and Arguments usually have sub-fields.

User-defined Fields

These fields are defined in Studio by using the Add Log Fields activity and appear in all subsequent logs after the activity is generated, unless they are removed by the Remove Log Fields activity.

Note:

Creating custom log fields that have the same name as a default log field causes the logging process to become corrupted and may cause issues in the workflow you are running.

For example, creating a custom log field called jobId causes this issue, as jobId is a log field that is generated by default.

On this page

Logging Levels in UiPath
Log Message Types
Default Logs
User-Defined Logs
Log Fields
Default Fields
Type-specific Fields
User-defined Fields

Was this page helpful?

PREVIOUSManaging Logs in Orchestrator

NEXTOrchestrator Logs