- 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
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Studio Logs
Studio Traces
The Studio Traces are diagnostic log messages generated by Studio, containing information related to its behavior.
The logging level settings and log file path can be modified by editing the <Installation Folder>\Studio.NLog.config
file. If this file does not exist, it is automatically created when an event occurs. The section can be found under the <nlog>
tag.
UiPath Studio Traces Logging Level
The default selected minimum logging level for Studio is Warn
(Warning), but more levels can be added or excluded in the same configuration file.
To only log Error and Warning levels, specify them in between the <rules>
tag, like in the example below:
<rules> <logger name="*" level="Error" writeTo="AsyncTarget" />
<logger name="*" level="Warning" writeTo="AsyncTarget" /> </rules>
To limit the logs to a specific size, set the archiveAboveSize="<value in bytes>"
in the <target>
section:
<target name="AsyncTarget" xsi:type="AsyncWrapper" minlevel = "Off"> <target name="logfile" xsi:type="File" fileName="${logDirectory}/${shortdate}_Studio.log"
layout="${time} => [${level:uppercase=true}] [${logger}] [${threadid}] ${message}" archiveAboveSize="<value in bytes>/> </target>
To disable logging, simply set the minlevel
tag to ”Off”
, as you can see below:
<rules> <logger name="*" minlevel="Off" writeTo="AsyncTarget" /> </rules>
Targets of the UiPath Studio Traces
The default log file path for Studio is %localappdata%\UiPath\Logs\<shortdate>_Studio.log
. The format for <shortdate>
is yyyy-mm-dd
.
To change the log file path, simply change the value of the logDirectory
parameter with the path you want to use.
For example, to move the log file path to the Desktop, modify the value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs"
parameter to value="${specialfolder:folder=DesktopDirectory"
.