- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot Logs
- Logging and Log Levels
- Robot JavaScript SDK
- Specific Scenarios
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Restarting Robot Components
- Troubleshooting
- About Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
Robot Logs
Logs are time-stamped files which contain informational events, error and warning messages relevant to the application.
C:\Windows\System32\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data
), within the available disk space, until the connection is restored. When the connection is restored, the logs are sent in
batches in the order they had been generated.
The status of a job is stored in the memory of the UiPath Robot service. When Orchestrator becomes available, the information regarding the job status is synced between the two. However, if Orchestrator is not available and you restart the UiPath Robot service, the information is lost. This means that whenever Orchestrator becomes available the job is executed again.
These logs provide information related to the Robot itself and its context. They are useful in identifying the cause of a specific error.
By default, Robot Diagnostic logs are enabled and any message with the Error or Warning levels is logged.
If other levels of logging information are needed, all of them can be enabled if Low Level Tracing is enabled. By default, this feature is disabled.
UiRobot.exe --enableLowLevel
in Command Prompt.
UiRobot.exe --disableLowLevel
in Command Prompt.
.etl
file. This enables verbose tracing for the Robot Executor and Service in the Event Viewer.
cd
argument, such as cd C:\Program Files\UiPath\Studio
.
We recommend enabling Low Level Tracing only while investigating a problem, and disabling it when the investigation session is over.
.etl
file containing the trace information is generated only after you disable the feature.
The Robot doesn’t need to be restarted for the changes to take effect.
<Installation Folder>\NLog.config
file. The Diagnostic logs are collected by the Internal type logger and are forwarded by using NLog targets.
NLog.config
:
<target xsi:type="EventLog" name="eventLog" layout="${callsite:className=false:includeSourcePath=true:methodName=false} ${message}"
source="UiPath" log="Application" />
<logger name="Internal" minLevel="Trace" writeTo="eventLog" />
NLog.config
file requires administrator permissions. The UiRobot.exe service needs to be restarted if the Internal target is changed in the NLog.config
file for the changes to take effect.
This type of file can be opened from the Event Viewer:
- In Event Viewer, in the Actions panel, click Open Saved Log. The Open Saved Log window is displayed.
- Browse for the trace log file generated and click Open. The file is displayed in the left panel, under Saved Logs.
-
Select the file. Note that the contents of the logs are displayed.
Robot Execution Logs are messages generated by the execution of a process and typically contain information related to its behavior and user-defined messages.
There are several ways in which execution logs can be generated:
- The Write Line activity creates logs at the Trace level.
- The Log Message activity creates logs at the level that is specified in the Level property field.
- Executing an automation project generates logs that contain the behavior of each activity. These logs have the Trace level if the Level setting in the Orchestrator Settings window is set to Verbose.
The default logging level is controlled by the Level setting stored in Orchestrator Settings window. By default, it is set to Information.
- From the UiPath Assistant, go to the Preferences menu and then access Orchestrator Settings
-
Select the desired logging level from the Log Level drop-down menu, under the Logging section.
Note: If the Robot is installed as a Windows Service, administrator permission is required to edit this setting.
%LocalAppData%\UiPath\Logs
folder. The messages are collected by the WorkflowLogging logger and can be forwarded by using NLog targets, as specified by the following parameters in the NLog.config
file:
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" />
<rules>
<logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" />
</rules>
<targets>
<target type="File" name="WorkflowLogFiles" fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log" layout="${time} ${level} ${message}" keepFileOpen="true" openFileCacheTimeout="5" concurrentWrites="true" encoding="utf-8" writeBom="true" />
</targets>
</nlog>
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" />
<rules>
<logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" />
</rules>
<targets>
<target type="File" name="WorkflowLogFiles" fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log" layout="${time} ${level} ${message}" keepFileOpen="true" openFileCacheTimeout="5" concurrentWrites="true" encoding="utf-8" writeBom="true" />
</targets>
</nlog>
If the Robot is connected to Orchestrator, all execution logs are sent to Orchestrator and can be seen in the Logs page.
<Installation Folder>\NLog.config
file.
To avoid creating a large amount of log files consuming disk space on the machine, you can choose to archive log files once a specific number files has been reached.
<target>
tag:
- archiveNumbering="Date"
- archiveEvery="Day"
- archiveDateFormat="yyyy-MM-dd"
- archiveFileName="${WorkflowLoggingDirectory}/{#}_Execution.log"
-
maxArchiveFiles="10"
<?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" /> <rules> <logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" /> </rules> <targets> <target type="File" name="WorkflowLogFiles" fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log" layout="${time} ${level} ${message}" keepFileOpen="true" openFileCacheTimeout="5" concurrentWrites="true" encoding="utf-8" writeBom="true" archiveNumbering="Date" archiveEvery="Day" archiveDateFormat="yyyy-MM-dd" archiveFileName="${WorkflowLoggingDirectory}/{#}_Execution.log" maxArchiveFiles="10" /> </targets> </nlog>
<?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" /> <rules> <logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" /> </rules> <targets> <target type="File" name="WorkflowLogFiles" fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log" layout="${time} ${level} ${message}" keepFileOpen="true" openFileCacheTimeout="5" concurrentWrites="true" encoding="utf-8" writeBom="true" archiveNumbering="Date" archiveEvery="Day" archiveDateFormat="yyyy-MM-dd" archiveFileName="${WorkflowLoggingDirectory}/{#}_Execution.log" maxArchiveFiles="10" /> </targets> </nlog>Note: ThemaxArchiveFiles
is the parameter controlling the number of archive files.Note: Editing theNLog.config
file requires administrator permissions. The robot service does not need to be restarted for the changes to take effect.
UiPath.Executor.exe.config
file, which can be found in the C:\Program Files\UiPath\Studio
folder. To do this, XML code must be added under the <system.serviceModel>
tag. For example:
<tracking>
<profiles>
<trackingProfile name="StandardProfile">
<workflow>
<activityStateQueries>
<activityStateQuery activityName="*">
<states>
<state name="Faulted"/>
</states>
<arguments>
<argument name="*"/>
</arguments>
<variables>
<variable name="*"/>
</variables>
</activityStateQuery>
</activityStateQueries>
</workflow>
</trackingProfile>
</profiles>
</tracking>
<tracking>
<profiles>
<trackingProfile name="StandardProfile">
<workflow>
<activityStateQueries>
<activityStateQuery activityName="*">
<states>
<state name="Faulted"/>
</states>
<arguments>
<argument name="*"/>
</arguments>
<variables>
<variable name="*"/>
</variables>
</activityStateQuery>
</activityStateQueries>
</workflow>
</trackingProfile>
</profiles>
</tracking>
<states>
tag contains only <state name="Faulted"/>
, inserting the above code enables only the activities which have the Faulted state to be logged. Adding other parameters under the <states>
tag, such as <state name="Executing"/>
causes activities that have other states to be logged as well.
Not only activity states can be modified, but also other things, such as variables and arguments. More information about customization can be found here.
UiPath.Executor.exe.config
file requires a restart of the Robot service for the changes to take effect.
- Robot Diagnostic Logs
- Enabling Robot Diagnostic Logs
- Targets of the Robot Diagnostic Logs
- Opening the .etl log file
- Robot Execution Logs
- Execution Logs Logging Level
- Changing the Default Logging Level From the Orchestrator Settings Window:
- Targets of the Execution Logs
- Deleting old log files
- Further Editing of Logs