- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- StudioPro
- Extensions
- Troubleshooting
Types of Logs
The UiPath Platform has logging capabilities for all of its main components. All of the UiPath specific logs are based on the Nlog infrastructure.
These logs can be classified by several characteristics, as follows:
Judging by the log category, which describes whether the log message was designed by the user or is automatically generated by the system, logs can be:
-
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. The events logged by this category are:
- Execution Start is generated every time a process is started (Level = Information)
- Execution End is generated every time a process is finalized (Level = Information)
- Transaction Start is generated every time a transaction within a process is started (Level = Information)
- Transaction End is generated every time a transaction within a process is finalized (Level = Information)
- Error Log is generated every time the execution encounters an error and stops (Level = Error)
- Debugging Log (Level = Trace) is generated if the Robot Logging Setting is set to Verbose and contains, activity names, types, variable values, arguments etc.
- 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.
These log fields are present in all 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 (defined in Orchestrator)
Note: The processName and processVersion might not appear if the process is run locally without connection to the Orchestrator.
These log fields are present depending on the log type:
- totalExecutionTimeInSeconds for Execution End
- totalExecutionTime for Execution End
- queueName for Transaction Start and Transaction End
- transactionID for Transaction Start and Transaction End
- transactionState for Transaction Start and Transaction End
- transactionStatus for Transaction End
- transactionExecutionTime for Transaction End
-
activityInfo for Debugging Log. It is a JSON message with the following fields
- DisplayName
- State (Faulted, Closed, Executing)
- Activity
- Variables
-
Arguments
Note: Only the first 3 are always present in the message. Variables and Arguments usually have sub-fields.
