# May 2026

> May 2026 release notes for Maestro in Automation Cloud.

## May 29, 2026

### Process Repository is now generally available

The Process Repository feature is now generally available. The Process Repository provides a dedicated space in Automation Hub for documenting and governing your organization's business processes — separate from the automation pipeline. Business process entries are organized through a capability map that reflects your organizational taxonomy, support BPMN process map authoring, and can be linked to Studio Web solutions. With this release, the Process Repository also gains a built-in BPMN modelling editor, versioning for process maps, and collaborative commenting.
For more information, see [About the Process Repository](https://docs.uipath.com/automation-hub/automation-cloud/latest/user-guide/about-the-process-repository).

## May 28, 2026

### Notification Service task

BPMN workflows can now send UiPath Notification Service events as an explicit process step using the `Maestro.NotificationService` service task. Workflow authors specify the notification topic, recipients (users or groups identified by GUID), priority, and message body. The notification is dispatched using the Worker's existing service identity, with no additional credentials required.

Previously, notifications were only available through the built-in case management alert path, with no control over recipients or topic.

For more information, see [Service task](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/service-task).

### Orchestrator job failure error messages

Maestro now shows more specific error messages when an Orchestrator job fails to start. Instead of always showing the generic "Failure to start the Orchestrator RPA job" message, Maestro now identifies the specific job type — for example, "Failure to start the Orchestrator Agent job" or "Failure to start the Orchestrator Function job".

## May 25, 2026

### hitlTask output variable for Human-in-the-Loop tasks

When a Human-in-the-Loop (HITL) task completes, Maestro now exposes the full task response as a `hitlTask` output variable alongside the existing Action output. Previously, workflows could only read the action the completing user took. Downstream steps can now read all task details from the App Tasks API response, including assignee information and the task key.

For more information, see [User task](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/user-task).

### IXP Extraction activity: jobAttachment digitization mode

The IXP Extraction activity now accepts a `jobAttachment` digitization mode in addition to the existing `fileUpload` mode. In `jobAttachment` mode, the attachment identifier, file name, and MIME type are supplied as individual inputs. Workflows that receive job attachments directly from Orchestrator can now invoke document extraction without first resolving a `downloadedFileOutput` reference. Workflows that supply an unrecognized mode receive the error code `IdpDigitizationModeNotSupported` instead of a generic input validation error.

### Reduced write overhead for high-throughput workflows

Maestro now excludes unbounded and large-data paths — such as run history arrays and AI recommendation arrays — from Cosmos DB indexing on the Instance, ElementExecution, and Incident containers. This lowers write request unit (RU) consumption for high-throughput workflows, especially multi-instance subprocesses and case management scenarios. Maestro reconciles existing containers to the new indexing policy on startup — no action required.

### Bug fix

- Fixed a runtime exception that occurred when recording activity errors if a log field's string representation was null. Error-logging paths now handle null values gracefully.