- 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
- Automating Citrix Technologies
- 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 packages and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Chrome 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
- Edge 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
Signing in to Your Account
UiPathStudio.msi installer with the Robot in user mode, you can connect Studio and the Assistant to Orchestrator by signing in to your UiPath account:
- Click
on the upper-right side of the Studio window, and then click Sign in. To find out more information about signing in, click Learn more.- To use a custom URL instead of the default
https://cloud.uipath.com, enter the URL in the Service URL field. - To connect to Orchestrator with client credentials or machine key, click More Options > Connect to Orchestrator.
-
To activate a local license key, click More Options > Standalone Options.
- To use a custom URL instead of the default
After you sign in, an icon with your initials is displayed on the upper-right side of the Studio window. To sign out and disconnect from Orchestrator from both Studio and the Assistant, click the icon, and then select Sign Out.
UiPathStudio.msi installer with the Robot registered as a
Windows service, you can connect to Orchestrator with your client credentials or
machine key:
-
Click , and then click Connect.
This section documents errors you may encounter when you try to sign in to your account. Select an error to view information about its cause and available solutions.
Interactive sign-in is not enabled for this tenant. Enable it from the Orchestrator settings, or connect using the machine key.
Cause
Authentication is not enabled in the tenant you are trying to sign in to. This may occur if the tenant was created in an older version of Orchestrator, before the introduction of the interactive sign-in feature.
Solution
Do one of the following:
-
In Orchestrator, go to Tenant > Settings > Security , and then select Allow both user authentication and robot key authentication.
Note: Only an administrator can perform this task. - In the Studio Sign-in screen, select More Options > Connect to Orchestrator to connect using your machine key instead.
Cause
The Robot is installed in service mode. Interactive sign-in is supported only if the Robot is installed in user mode.
Solution
Do one of the following:
- Run the installation again and make sure to select the User mode Robot installation type. For more information, see Install Studio.
- In the Studio Sign-in screen, select More Options > Connect to Orchestrator to connect using your machine key instead.
Cause
You are trying to sign in but no attended robot is configured for your user in Orchestrator.
Solution
In Orchestrator, edit the current user, select the option to create an attended robot for the user, and select a developer license type for which a license is available. You can check license availability by going to Tenant > License.
Cause
You are using a classic robot defined in Orchestrator using the classic method or via the Windows user and you are already connected to Orchestrator with a machine key. When you then sign in from Studio, a different username is sent to Orchestrator
Solution
Do one of the following:
- Sign out, and then, in the Studio Sign-in screen, select More Options > Connect to Orchestrator to connect using your machine key.
-
In Orchestrator, set up a modern robot configuration instead of the classic one, and then sign in again.
Note: Only an administrator can perform this task.
Cause
You are trying to sign in but your user is not properly configured to acquire a license from Orchestrator.
Solution
In Orchestrator, edit the current user, make sure the option to create an attended robot for the user is selected, and select a developer license type for which a license is available. You can check license availability by going to Tenant > License.
Cause
Connection to Orchestrator could not be established.
Solution
Make sure your Internet connection is working.
Cause
You are trying to sign in but your IP address is restricted in Automation Cloud.
Solution
Add your IP address to the list of trusted IP ranges. For more information, see Restricting access by IP in the Automation Cloud Admin Guide.
- Connecting to Orchestrator With Client Credentials or Machine Key
- Common Sign-in Errors
- Interactive sign-in is not enabled for this tenant. Enable it from the Orchestrator settings, or connect using the machine key.
- Interactive connect is not available.
- No robot configured for the current user.
- Robot does not exist.
- Cannot acquire a license.
- No such host in known.
- Accessing the organization from an untrusted network.
