- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- 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-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- 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
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- 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 Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
Opting Out of Telemetry
UiPath collects usage and performance data to help diagnose problems and improve its products. For more details about UiPath’s privacy practices, please review the privacy statement.
The telemetry data is used for developing new features and improvements for boosting user-experience and equipping Studio and the Robot with the tools that you need the most.
In addition, by using telemetry data we can cater to user needs and make improvements in the product, in such a way that it would make it easier for you to design, debug and run automation processes.
If you want to see how to opt out of telemetry in Orchestrator, please visit this page.
If you want to see how to opt out of telemetry on Mac, please visit this page.
To disable the collection of usage data for Studio and the Robot at install time, select a Custom installation > Advanced Settings, and select the Disable Telemetry option on the Security tab.
TELEMETRY_ENABLED=0 parameter for disabling telemetry. TELEMETRY_ENABLED=1 is the parameter for enabling data collection.
For example, the following command installs Studio, the user-mode Robot, Assistant, and opts out of telemetry:
UiPathStudio.msi ADDLOCAL=DesktopFeature,Studio,Robot TELEMETRY_ENABLED=0
TELEMETRY_ENABLED parameter can also be added when updating your Studio instance. If the parameter is omitted on updates, the previous value
is preserved.
TELEMETRY_ENABLED parameter during the update, Telemetry.Enabled is automatically set to true.
UiPathStudio.msi, you can opt out of telemetry at
user-level by using the Telemetry toggle in Studio Backstage view.
"Telemetry.Enabled" parameter in the
uipath.config file to be modified. Please note that this method is
recommended at organization level. Once the change is made in the
uipath.configfile, it can not be reverted by using the telemetry toggle in
Studio > General Settings.
In Studio Backstage view, go to Settings > General settings. Switch the two toggles under Telemetry to Disabled, and then restart Studio. Anonymous telemetry is no longer collected from your machine.
"Telemetry.Enabled" parameter in the uipath.config file,
located at %ProgramFiles%\UiPath\Studio\uipath.config.
<analyticsSettings>
<add key="Telemetry.Enabled" value="true" />
</analyticsSettings><analyticsSettings>
<add key="Telemetry.Enabled" value="true" />
</analyticsSettings><analyticsSettings> section, change the value for the
"Telemetry.Enabled" parameter from "true" to
"false". Save the file and restart Studio if needed. UiPath no longer
collects telemetry data pertaining to Studio and Robot installed on your machine.
analyticsSettings section to the uipath.config file, as
illustrated below:
<configSections>
<section name="analyticsSettings" type="System.Configuration.AppSettingsSection" />
</configSections><configSections>
<section name="analyticsSettings" type="System.Configuration.AppSettingsSection" />
</configSections>
