- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- About Dependencies
- Managing Dependencies
- Missing or Invalid Activities
- 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
- 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
- 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
Missing or Invalid Activities
Studio can display a workflow with activities that are missing or are invalid when problems were encountered (missing package or incorrect package version) during the import process.
Here are the situations when an activity can appear as missing or invalid:
- Package version newer than the one you have installed.
- Invalid project dependency; can occur when the dependency's version cannot be found due to different library versions.
- Missing project dependency.
There are two ways of verifying the root of the problem, checking the logs panel and checking the project's dependency tree.
Use this solution for verifying if the required package version corresponds to the installed one.
The easiest way of checking the errors displayed in the workflow is by examining the Output panel situated at the bottom of your Studio framework.
All errors are displayed in red and by reading the error you can easily identify the affected package.
The GIF below shows that the missing activity is named Get PDF Page Count and is part of the UiPath.Pdf.Activities package.
Another solution for solving the displayed errors is by verifying the project's dependencies. By selecting the project's root, you can see all packages and their dependencies included in the project.
The first step is to check if the package mentioned by the error is part of the project, and if so, to verify its version, and update it to the required one.
The below GIF explains how to check the dependencies.
A dependency can be invalid or missing.
- An invalid dependency can be solved by using the Repair Dependency option.
-
A missing dependency can be solved by searching and installing it directly from the Manage packages option.
Note: More information about Studio Logs can be found here.
After applying one of the above steps for identifying the problem, you can go ahead and fix it by installing a newer package or package version. All you need to do is to access the Manage Dependencies option and search for the desired package.
An example is shown in the below GIF:
