April 2025

UiPath Maestro™, which we announced as a public preview in March 2025, is now generally available. Maestro enables you to seamlessly integrate agents, robots and humans into complex, multi-system processes.

For details on using Orchestrator to leverage the capabilities of Maestro, refer to our initial announcement.

You can now create and monitor indexes in Orchestrator. Previously available in the AI Trust Layer interface, creating Context Grounding indexes is now integrated into Orchestrator. This simplifies the process and eliminates the need for organization administrator rights.

The new index management capabilities in Orchestrator provide a centralized point for management and monitoring at the tenant level. You can track query performance over specified time intervals, analyze index usage trends, and view a complete list of all indexes created within the tenant.

For details, refer to Indexes.

Orchestrator now allows you to create disconnected event triggers, which you define from scratch, outside of an existing process. The new functionality, previously available in Integration Service, complements the existing Orchestrator capability to edit connected triggers defined as package requirements for a process. Therefore, Orchestrator now provides a unified trigger experience, enabling you to create and manage all types of triggers.

For details on creating disconnected event triggers, refer to Creating an event trigger.

When you navigate to Tenant in the user interface, Monitoring is now displayed as the landing page.

For more information, refer to Deploying agents.

When deploying an agent, you can now enable agent memory. This allows the agent to retain information, learn from past interactions, and apply the acquired knowledge to future tasks.

For information on enabling agent memory, refer to Deploying agents.

For a detailed explanation of agent memory, refer to the Agents documentation.

Additionally, for agentic processes, you can use the Agentic process link in the panel to explore the process in Maestro.

We have enhanced the Job details tab to make the input and output move visible.

Additionally, the Runtime details section of the tab now provides more detailed information.

For agentic process jobs, the panel also includes a Maestro link that allows you to explore the process instance in Maestro.

For more information, refer to Viewing job details.

For agent and agentic process jobs, you can now view the job trace in the job details panel, under a dedicated tab. The trace provides a comprehensive, hierarchical view of the job run, its input and output, as well as any other resources invoked or jobs executed in connection with the run.

The trace view also allows you to provide positive or negative feedback, as well as comments, on any of the trace items.

As we announced in Entry point selection when starting a job temporarily not possible, we temporarily disabled the feature due to a bug. We have now fixed the bug, and you can use the feature normally.

For more information, refer to Starting a job.

You can now start a job using the Run as Myself (Personal automation) option if your user inherits appropriate tenant-level and folder-level access configurations from a group that the user is part of. Previously, you could use the Run as Myself (Personal automation) option to start a job only if an administrator had assigned a specific access configuration to your user in that folder.

In the Start Job window, if the job cannot start because a suitable account is not assigned to the folder, you receive an error message explaining the issue. Also, the Assign an account to the folder button is highlighted.

Additionally, selecting Assign an account to the folder now allows you to create a new account on the fly and assign the appropriate roles to the account. You can then resume the Start job workflow.

For further information, refer to Starting a job.

Exports you downloaded were always in English, regardless of the language you selected in the Orchestrator preferences. The issue no longer occurs.

As we announced in Migration of mixed roles, the migration process for enterprise customers will begin soon. For details, refer to the following table:

As previously announced in our Deprecation timeline, this week, we are starting the migration of mixed roles across all Community tenants. The migration involves the following changes:

We will announce the migration schedule for enterprise customers soon.

In March 2025, we announced a new feature that allowed you to select the entry point when starting a job.

However, due to a bug, we temporarily disabled the feature. We are working on re-enabling it soon.

As we previously announced in Retention policy updates, we are starting a gradual rollout of the new retention policies for uncompleted jobs and queue items. Going forward, the system will archive or delete uncompleted jobs and queue items according to the retention intervals you set.

For more information on the new retention policies, refer to the following documentation:

If you attempt to update the number of runtimes allocated to a machine template to a lower value than the number of jobs currently executing on any machine connected to the template, you receive an error message.

To avoid accidental deletions, strong confirmation on delete is now always enabled, and the option to disable it is no longer available.

We have made the following changes in the Packages tab under Tenant:

For further information, refer to Tenant feed.

We have made the following changes to the Jobs grid under Automations, at folder level:

For further information, refer to About jobs.