- 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-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
- Control Flow
- Object Repository
- Logging
- The ScreenScrapeJavaSupport Tool
- Studio testing
- Extensions
- Troubleshooting
- 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
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Cannot communicate with the browser, please check the UiPath extension
error can indicate one of the following issues.
Cannot communicate with the browser, please check the UiPath
extension error message, the first step to take is to Check if the Extension for Microsoft Edge is installed and enabled.
Description
The native host must be running to enable the communication between the Robot and the UiPath Extension.
Solution
Use the following checklist to ensure the native host is running:
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Check if the antivirus software
blocks access to
ChromeNativeMessaging.exe. To fix this issue, add the following folder to the antivirus allowlist:-
C:\Program Files (x86)\Common Files\UiPath\UiPath.Common– if you're using Studio version 2023.10 and newer. -
C:\ProgramData\UiPath\UiPath.Common– if you're using Studio versions older than 2023.10.
-
Description
The browser extension can fail to initialize on slow machines with high CPU usage. This issue can have one of two causes:
- The Open Browser activity has an insufficient timeout.
- In some cases, this Chromium bug can cause the extension to fail to initialize and the browser must be restarted. This issue affects all browser extensions.
Solution
Increase the Open Browser timeout. You can find more details on how to do that in the Known Issues Specific to MV3 Extensions page under the Open Browser activity has insufficient timeout section.
If you’ve increased the timeout and the issue persists, set to True the Enable retry setting introduced with UI Automation version 2023.10 in Project Settings > UI Automation Classic > Browser > Enable retry for OpenBrowser Edge.
When this setting is enabled, the Open Browser logic restarts the browser several times if the Native Host failed to initialize within the given timeout.
The browser extension may be corrupted due to a roaming user profile. For more information on roaming user profiles, see the Windows official documentation.
To solve this issue, see The extension may have been corrupted.
