robot
2025.10
false
Robot admin guide
- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for High-Density Robots
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Using EntraID users with multifactor authentication (MFA) for unattended robots
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting
Reference for all fields in a UiPath Robot log entry, including message, level, timestamp, filename, and job-specific properties.
A log entry contains several log fields, each holding a different information about the vent being logged.
Default fields
- Message - The log message.
- Level - Defines the log level.
- Timestamp - The exact date and time the logged action was happened.
- FileName - The name of the
.xamlfile being executed. - jobId (*) - The ID of the job running the process.
- processName (*) - The name of the process that triggered the logging. Requires an active connection to Orchestrator.
- processVersion (*) - The version number of the process. Requires an active connection to Orchestrator.
- windowsIdentity - The name of the user that performed the action that was logged.
- robotName (*) - The name of the Robot (as defined in Orchestrator).
- machineName - The name of the robot machine.
- machineId (*) - The id of the robot machine.
- organizationUnitId * - The ID of the Orchestrator organization.
(*) These log fields cannot be overridden using the Add Log Fields activity.
User-defined fields
To define custom fields, use the Add Log Fields activity. These fields appear in all subsequent logs. To remove these fields from further logs, use the Remove Log Fields activity.
Important:
Make sure to name your custom log fields different from the default log fields. Otherwise, duplicate names can corrupt the logging process and disrupt the execution of your workflow.
Type-specific fields
These logs are present depending on the log type.
For the Execution End default log, the following fields are included:
- totalExecutionTimeInSeconds
- totalExecutionTime
For the Transaction Start default log, the following fields are included:
- queueName
- transactionID
- transactionState
- initiatedBy
For the Transaction End default log, the following fields are included:
- queueName
- transactionID
- transactionState
- transactionStatus
- transactionExecutionTime
- processingExceptionType
- processingExceptionReason
- queueItemReviewStatus
- queueItemPriority
For the Debugging Log default log, the following fields are included:
- activityInfo, which is a JSON message with the following fields:
- DisplayName
- State(Faulted,Closed,Executing)
- Activity
- Arguments
- Default fields
- User-defined fields
- Type-specific fields
- For the Execution End default log, the following fields are included:
- For the Transaction Start default log, the following fields are included:
- For the Transaction End default log, the following fields are included:
- For the Debugging Log default log, the following fields are included: