- 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-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Properties
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-017 - Invalid parameter modifier
- 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
- Troubleshooting
- Trigger-based Attended Automation
- Object Repository
- The ScreenScrapeJavaSupport Tool
- 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 Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Studio testing
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- 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
- Validation of large Windows-legacy projects takes longer than expected
v26.10
26.10 release notes for Activity Migrator.
26.10.0
Release date: November 16, 2026
Requirements and download
The Activity Migrator now runs on .NET 10. To use version 26.10.0, install the .NET 10 Desktop Runtime (x64). Any 10.0.x version is supported. After you install 26.10.0, the .NET 8 runtime is no longer required.
The download package is significantly smaller, at the same download link.
Migration of Microsoft.Activities expression activities
The Activity Migrator now migrates Microsoft.Activities 1.0.1 expression activities: SplitString, ContainsString, ReplaceString, ParseDate, CompareDate, CreateDate, DateInRange, GetDictionaryValue, BuildDictionary, GetItemFromCollection and CreateException.
Each of these activities is replaced with an Assign activity with an equivalent VB or C# expression, depending on the project language. If an activity can’t be expressed as an Assign, it is left unchanged, and the migration report explains why.
Automatic package references
The Activity Migrator now adds missing NuGet package references to migrated projects automatically. Projects that use any of the following namespaces receive the matching packages, so they build without manual fixes:
System.Data.SqlClientSystem.Data.OdbcSystem.Data.OleDbSystem.ServiceProcessSystem.ManagementSystem.DirectoryServices
Detection covers expressions, type arguments (for example, in Catch blocks), and code in Invoke Code activities.
Redesigned migration report
The HTML migration report has a new layout with Overview, Projects, Workflows, Findings, and Run details tabs. You can filter and search the results, view each changed activity before and after migration, and switch between light and dark mode. For bulk migrations, an all-projects view lists the projects that need attention first.
The report requires a recent browser, such as Microsoft Edge or Google Chrome version 123 or later.
To learn more, refer to Migration report.
Bug fixes
- Empty strings in arrays, lists, and dictionaries were removed during migration, which prevented the migrated workflow from opening. Empty strings are now preserved.
- Reference fixing worked only on Windows systems with English as the display language. It now works in any Windows display language.
- Types that share the same short name were sometimes resolved to the wrong package. They now resolve to the correct one, for example
WorkbookApplicationfromUiPath.Excel.Activities.