robot
2024.10
true
Robot admin guide
Last updated Nov 12, 2024

Log storage

Orchestrator storage

When the Robot is connected to Orchestrator, only logs matching the level set in Assistant or Orchestrator appear on the Logs page. If Orchestrator is unavailable, logs are stored in a local path - 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.

NLog storage

Important:

The Robot update overwrites and resets this file, removing any prior edits.

Additionally, log storage can be configured by editing the NLog.config file. Diagnostic logs are collected by the Internal type logger and are forwarded by using NLog targets. By default, execution logs are stored in a file in the %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>

Log storage by Robot mode

Robot logs are stored differently, based on the user running the automation, which can be the local user (for User Mode robots), or the Local System user (for Service Mode robots):

Log type

Storage for Service Mode robots

Storage for User Mode robots

Execution logs in .log format

C:\Users\user\AppData\Local\UiPath\Logs

%LocalAppData%\UiPath\Logs

Execution logs in LiteDB format

C:\Windows\System32\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data

%LocalAppData%\UiPath\Logs\execution_log_data

Diagnostic (or internal) logs

%ProgramData%\\UiPath\Logs\internal

%LocalAppData%\UiPath\Logs\internal

Update logs

%ProgramData%\UiPath\UpdateService\Logs%LocalAppData%\UiPath\UpdateService\Logs
  • Orchestrator storage
  • NLog storage
  • Log storage by Robot mode

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.