- Release notes
- 2.2510.1
- 2.2510.0-patch2
- Before you begin
- Managing access
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Structure of transformations
- Tips for writing SQL
- Exporting and importing transformations
- Viewing the data run logs
- Merging event logs
- Configuring Tags
- Configuring Due dates
- Configuring fields for Automation potential
- Activity Configuration: Defining activity order
- Making the transformations available in dashboards
- Data models
- Adding and editing processes
- Customizing dashboards
- Publishing Dashboards
- App templates
- Notifications
- Additional resources
Process Mining
Release date: March 16, 2026
This patch resolves issues affecting data loading and application editing in Process Mining deployments with large datasets.
Uploading data failed for applications with a large number of columns. During data operations, Process Mining queries the database to retrieve column names and data types. For applications with many columns, the resulting output exceeded the 8,000-character limit in Microsoft SQL Server, which caused the upload to fail with a SQL error. Process Mining now handles large column sets correctly and data uploads succeed as expected.
Applications with more than 500 fields could no longer be edited. Process Mining enforces a 500-field limit per application. During the initial run, the system automatically added newly discovered fields. Incorrect field counting allowed the total to exceed the limit, after which the application could not be saved or edited. Field counting now works correctly, and applications remain editable within the defined limit.
Data refreshes after the initial CDATA ingestion did not load new data into the ELT editor or dashboards, with no error reported. When the data mapping was unchanged between ingestions, an incorrect check bypassed the mapping execution step for CDATA tables, which write directly to the database rather than through blob storage. As a result, subsequent ingestions appeared to complete successfully but continued to display data from the initial ingestion. The check is now corrected, and CDATA data refreshes load updated data as expected.