- 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
Known issues specific to MV3 extensions
Simulate input method no longer works on HTML elements that
have a click handler with javascript: URI.
In this case, the simulated click will not take effect and no errors will reported.
This was reported as a Chromium bug. This issue is quite rare as very few HTML elements have click handlers in this form.
Workarounds
Two workarounds are available for this issue:
- Identify the failing Click activity in your workflow and change the input method from Simulate to any other input method (Chromium API, Hardware Events, Window Messages).
- Upgrade to UiPath.UIAutomation.Activities package v22.12 or newer and use the Enable workaround for simulate click with MV3 extension option in Project Settings.
The DeveloperToolsAvailability has the following possible values:
- 0 = Disallow usage of the Developer Tools on extensions installed by enterprise policy, allow usage of the Developer Tools in other contexts
- 1 = Allow usage of the Developer Tools
- 2 = Disallow usage of the Developer Tools
1 to
enable the full functionality of the extension.
This value is automatically set correctly when the extension is installed but it will be overwritten if your system administrator has set another value for this policy.
The other values for DeveloperToolsAvailability cause the problems listed below.
0
then:
- The UiPath Extension for Edge will be restricting to working with LTS versions of UiAutomation (19.10.x, 20.10.x, 21.10.x, 22.4.x)
- The
InjectJSActivity will not work.
2
then:
- All the limitations from
DeveloperToolsAvailability=0apply - The
ChromiumAPIinput method will not work.
ChromeNativeMessaging.exe could not
be started:
Cannot communicate with UiPath Platform
The native part of the extension is not configured correctly.
Re-install the extension from UiPath Studio.
jQuery $ , or to interact with page code (e.g.,
window.alert). The Inject Js Script activity won't
report an error, but the script will fail to execute and the following error will be
reported in the browser DevTools (F12): "Refused to execute inline script because it
violates the following Content Security Policy directive."
This is a limitation introduced by the MV3 platform.
To fix this issue, select the Execution world - Page option from the Inject Js Script activity.
Your existing JavaScript code doesn't require any changes, and by using the Execution world - Page option it will work for both MV2 and MV3 extensions.
For MV3 extensions, the browser loads the extension later, after the web pages have loaded. This means that on slower machines, the Open Browser activity from UiPath.UiAutomation.Activities version 22.10 or older can reach the internal timeout of 20 seconds before the extension has started.
Starting with v22.12.0-preview, the internal timeout for the Open Browser activity has been increased from 20 seconds to 60 seconds.
Since you may need to set a longer timeout for the browser startup, it is now configurable from the Use Application/Browser and Open Browser activities. The following project settings have been added:
-
UI Automation Classic → Browser → Open browser timeout (seconds)
-
UI Automation Modern → Application/Browser → Open browser timeout (seconds)
UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable. For
example, set UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS=120 to use 120
seconds for the activity's timeout.
- Click activity with Simulate fails on specific web page elements
- The DeveloperToolsAvailability Group Policy value must be set to 1
- The UiPath Web Automation browser window shows a warning
- The Inject Js Script activity can no longer be used to access page variables and code
- Open Browser activity has an insufficient timeout
