studio

2020.10

false

Release Notes
- 2020.10.2
- 2020.10.4
- 2020.10.6
- 2020.10.7
- 2020.10.8
- 2020.10.9
- 2020.10.10
- 2020.10.11
- 2020.10.12
- 2020.10.13
- 2020.10.14
- 2020.10.15
Getting Started
- Introduction
- The User Interface
- Keyboard Shortcuts
- Configuring Studio Settings
- Project Templates
  - Orchestration Process
  - Background Process
  - Robotic Enterprise Framework
  - Transactional Process
  - Trigger Based Attended Automation
- Creating a Basic Process
- Creating a Basic Library
- Tutorials
Setup and Configuration
- Hardware and Software Requirements
- Install Studio
  - Services Studio Connects To
- Activate Studio
  - About Licensing
- Update Studio
- Command Line Parameters
- Supported Applications and Technologies
- Enabling Gmail for Email Activities
- Opting Out of Telemetry
Automation Projects
- About Automation Projects
- About Publishing Automation Projects
  - Publishing Projects From Studio
  - Publishing Projects from the Command Line
- About Libraries
  - Loading Web Services in Libraries
- Managing activity packages
- Configuring Activity Project Settings
- Signing Packages
- Governance
- Importing Entities
- Modern Design Experience
Dependencies
- About Dependencies
- Managing Dependencies
- Project Dependencies Mass Update
  - Mass Update Command Line Parameters
- Missing or Invalid Activities
Types of Workflows
- Sequences
- Flowcharts
- State Machines
- Global Exception Handler
File Comparison
- About File Comparison
- Comparing Files
Automation Best Practices
- Workflow Design
- UI Automation
- Project Organization
- Automation Lifecycle
Source Control Integration
- About Version Control
- Managing Projects With GIT
- Managing Projects With TFS
- Managing Projects With SVN
- Workflow Diff
Debugging
- About Debugging
  - Test Activities
  - Debugging Actions
  - The Locals Panel
  - The Call Stack Panel
  - The Breakpoints Panel
  - The Watch Panel
  - The Immediate Panel
The Diagnostic Tool
- About The Diagnostic Tool
Workflow Analyzer
- About Workflow Analyzer
- Naming Rules
  - 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
- Design Best Practices
  - 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
- Project Anatomy Rules
  - ST-ANA-003 - Project Workflow Count
  - ST-ANA-005 - Check Project.json Exists
  - ST-ANA-006 - Main Workflow Exists
  - ST-ANA-009 - File Activities Stats
- Maintainability and Readability Rules
  - ST-MRD-002 - Activity Name Defaults
  - ST-MRD-004 - Unreachable Activities
  - ST-MRD-005 - Redundant Sequences
  - ST-MRD-007 - Nested If Clauses
  - ST-MRD-008 - Empty Sequence
  - ST-MRD-009 - Deeply Nested Activities
  - ST-MRD-011 - Write Line Usage
  - ST-MRD-017 - Incomplete If
- Usage Rules
  - 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
- Performance and Reusability Rules
  - ST-PRR-004 - Hardcoded Delay Activity
- Reliability Rules
  - ST-REL-006 - Infinite Loop
- Security Rules
  - ST-SEC-007 - SecureString Argument Usage
  - ST-SEC-008 - SecureString Variable Usage
  - ST-SEC-009 - SecureString Misusage
Variables
- Managing Variables
- The Variables Panel
- Types of Variables
  - Text Variables
    - Example of Using a Text Variable
  - True or False Variables
    - Example of Using a True or False Variable
  - Number Variables
    - Example of Using a Number Variable
  - Array Variables
    - Example of Using an Array Variable
  - Date and Time Variables
    - Example of Using a Date and Time Variable
  - Data Table Variables
    - Example of Using DataTable Variables
- UiPath Proprietary Variables
Arguments
- Managing Arguments
- The Arguments Panel
- Using Arguments
Imported Namespaces
- About Imported Namespaces
- Importing New Namespaces
Control Flow
- About Control Flow
- Control Flow Activities
  - The Assign Activity
  - The Delay Activity
    - Example of Using the Delay Activity
  - The Do While Activity
    - Example of Using a Do While Activity
  - The If Activity
    - Example of Using an If Activity
  - The Switch Activity
    - Example of Using a Switch Activity
  - The While Activity
    - Example of Using a While Activity
  - The For Each Activity
    - Example of Using a For Each Activity
  - The Break Activity
    - Example of Using a Break Activity
Object Repository
- About Object Repository
- Creating an Object Repository
- Reusing Objects and UI Libraries
Logging
- Studio Logs
- Setup Logs
- OCR Diagnostic Logs
- Logging Levels
- Types of Logs
- Protecting Sensitive Information
The ScaleCoordinates Migration Tool
- Best Practices and Limitations
- Example of Using the ScaleCoordinates Migration Tool
The ScreenScrapeJavaSupport Tool
- About the ScreenScrapeJavaSupport Tool
- Argument Descriptions for the ScreenScrapeJavaSupport Tool
StudioPro
- Introduction
- Application Testing
- RPA Testing
- API Test Automation
- Mock Testing
Extensions
- About extensions
- SetupExtensions tool
- UiPath Remote Runtime
- Extension for Chrome
  - Group Policies
  - Troubleshooting
- Extension for Edge
  - Group Policies
  - Troubleshooting
- Extension for Firefox
  - Troubleshooting
- Extension for Java
  - Troubleshooting
- Extension for Silverlight
  - Troubleshooting
- Extension for Citrix
  - Automating Citrix Technologies
- Extension for Windows Remote Desktop
- Extension for VMware Horizon
- Extension for Microsoft Edge Legacy
  - Microsoft Edge Legacy Extension Troubleshooting
- SAP Solution Manager Plugin
- Excel Add-in
Troubleshooting
- Internet Explorer X64
- Microsoft Office Interop Issues
- Identifying UI Elements in PDF With Accessibility Options
- Identifying UI Elements After Windows Updates
- JxBrowser Applications
- User Events Monitoring
- Java in App-V
- Microsoft App-V Support and Limitations
- Citrix Troubleshooting

OUT OF SUPPORT

Studio User Guide

Last updated Oct 23, 2025

About The Diagnostic Tool

The UiPath Diagnostic Tool is a standalone utility, enabling you to better collect and preview diagnostics info, which is then packaged and can be sent to our technical support team to help you solve potential problems.

It comes bundled with a variety of collectors to help you gather just the information you need. Moreover, you can save selected collectors as a profile to be used later on. Information can be collected from Studio, Robot, RobotJS, Activities, and Orchestrator.

You can download the Diagnostic Tool from the Resource Center in your Automation Cloud instance.

It also comes installed with Studio, and you can find it in the C:\Program Files (x86)\UiPath\Studio folder. For Community installers, the tool is located in the %localappdata%\UiPath\Studio folder.

To access it, simply click the Start button, and search for the Diagnostics Tool application. Please note that this only works for UiPathStudio.msi deployments.

The Start Section

The Diagnostic Tool is based on profiles, which gather information using collectors. A profile is a set of collectors specialized in gathering specific information, depending on the issues you have. The tool comes with a couple of predefined profiles, each with a specific set of collectors, but it is also possible to create your own profiles, each suited for a particular issue. Even if you start of with a predefined profile, you can later on add or remove collectors, depending on what information needs to be gathered.

Profile	Description
Studio/Robot/Activities Issue	Gathers information about Studio, Robot, or Activities. This profile comes with several collectors enabled by default.
Orchestrator Issue	Gathers information about your connection to Orchestrator. This profile comes with several collectors enabled by default.
Empty Profile	This profile does not come with any selected collectors. Here is where you can create custom profiles with the desired collectors to use later on.
Custom Location	Gathers info based on a `.json` file you provide. You can select the collectors to be used.

Additionally, you can choose to import a previously generated .zip package of collected data to review.

The Configure Section

This section is where all the collectors are found. The first two profiles already have several collectors added, but you can also add others or remove existing ones. Available collectors are as follows:

Collector	Gathered Information
Registry Info	Registry keys used, as well as the corresponding value name and value data.
Screen Info	Display or displays used, as well as type, resolution, DPI, and offset coordinates.
Event Logs	Generates an `.evtx` log file for the selected application.
Environment Variables	System or local environment variables used, based on a configurable clause.
Computer Info	Name, domain, operating system, session, administrator, and proxy settings of the machine.
Log Files	Execution, Studio, ETL, and combined logs. They can be viewed and exported from each section.
Process Info	System processes used.
Third Party Installations	Enlists all the third party applications used.
UiPath Installs	Enlists all installed UiPath products on that machine, as well as the version, type, and path.
License	Displays the license type and status.
Settings File	Enlists the available `UiPath.settings`, `UiStudio.settings`, `UiStudio.v2.settings`, and `NuGet.config` files with the possibility to access them.
Orchestrator Web Config	Displays the `Web.config` file, based on the specified Registry Key location and its value.
Orchestrator Application Host File	Displays the `applicationhost.config` file based on a specified folder.

If you're not happy with the provided collectors of a profile, you can simply remove them by clicking the x button in the corresponding collector's container.

If you feel like you need more collectors, click the Add a New Collector button and choose the one you need from the list.

Considering you want to use some collectors multiple times, you can add them to the list and click the Export Profile to File button. This generates a .json file you can later on import from the Start section.

Some collectors allow you to view information in a more detailed manner.

For example, the Log Files collector lets you explore collected files of a log type (ExecutionLogs, StudioLogs, EtlLogs, or CombinedLogs) in a separate window, with the possibility to view a log file's path, open it, or even choose which of the log files to be exported.

Similarly, the Registry Info collector only displays the first few results in the Preview section, but allows you to view all results in a separate window, by clicking the Displaying x out of y button, there x is the displayed number of results, and y being the total.

The Preview Section

This is where all the collected information is displayed. They are grouped in collapsible boxes to make info easy to read. If you're not happy with particular collectors, you can simply disable them so they don't get exported in the final package.

Collectors you don't consider necessary for export can be disabled here. Simply uncheck the desired collectors before clicking Next.

The Export Section

The last section shows a preview of the collectors used in the process. All that's left to do now is to click on Export to save all collected data in a .zip package, with the possibility to open the location where the file is saved. You can also navigate between the sections if you want to make changes to collectors.

Command Line Arguments

The Diagnostic Tool can also be used from the Command Prompt or Windows PowerShell. The arguments and their results are the same, regardless of the usage mode.

It can be accessed as follows:

Command Prompt - open an elevated Command Prompt instance and use the cd command to the location of the Diagnostic Tool. Then, use one of the arguments enlisted below.
Windows PowerShell - navigate to the location of the Diagnostic Tool, right-click it, and choose to open in PowerShell. Then, use on of the arguments enlisted below.

Example:

UiPath.DiagnosticTool.exe run <[defaultProfile] | [pathToProfile> [Optional Parameter]

Argument	Description
`run studio`	Runs the Studio default profile.
`run orchestrator`	Runs the Orchestrator default profile.
`run <pathToFile>`	Runs a custom previously created, custom diagnostic profile from a generated `.json` file.
`-o, --output`	Specifies the output of the generated `.zip` package containing all the collected data.

On this page

The Start Section
The Configure Section
The Preview Section
The Export Section
Command Line Arguments

Was this page helpful?

PREVIOUSThe Immediate Panel

NEXTAbout Workflow Analyzer