studio
2023.10
false
- 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-021 - Hardcoded Timeout
- 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
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
Studio Logs
Studio User Guide
Last updated Nov 18, 2024
Studio Logs
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.
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>
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"
.
Note: Set the language for Windows keyboard to Japanese, Russian or French to make sure some Studio logs are localized in the respective
languages.