<img src="//trc.taboola.com/1222697/log/3/unip?en=page_view" width="0" height="0" style="display:none">


Knowledge Base

Logging Overview

UiPath 8 brings architectural changes that improve the overall reliability and performance. Workflow execution was moved from UiPath Studio application to UiRobot, our dedicated execution engine. 


UiRobot has a multi-process architecture similar to Chrome, that offers the option to execute each workflow in a separate UiRobot process, called Executor. Executors are managed by a special instance of UiRobot, simply called Robot. This way, if any Executor crashes, the main process won't be affected and it will continue running. 

Client Logging

UiPath relies on NLog, making it easy and flexible to integrate with databases, servers or any other NLog targets. Logging can be configured through NLog.config file. UiStudio, Robot and workflow execution generate log messages on the client side.

  • Messages produced by workflow execution are logged with Execution logging source. UiStudio logs as the Studio source.  Messages produced by the Robot instance or related to the management of the executors are logged with a Robot logging source.
  • By default, Execution and Studio logs are stored locally in %LocalAppData%/UiPath/Logs
  • All warnings and errors generated by Robot are saved to Windows Event Log, accessible via Windows Event Viewer
  • We have two activities that may be used for logging: Log Message and WriteLine. WriteLine activity logs with Trace level
  • An automatic logging mechanism for all execution steps, including the values of variables and arguments may be enabled in UiRobot.exe.config by setting LogParameters to 1 instead of 0 in <switches> section

Server Logging

If you have configured UiPath Server, all logs generated by Execution are also sent to the server. You can thus follow how each robot is doing in the Monitoring platform.