Orchestrator - May 2025

May 29, 2025

Rollout of new audit log retention policies

As we previously announced in Retention of audit logs, we are starting a gradual rollout of the following audit retention policies:

Audit logs are stored in the Orchestrator database for a duration extending to at least the last six months. During this time, they are visible and searchable in the interface, so there is no change in the user experience.
During the rollout, we will first create audit log archives for all calendar months, and then we will start gradually deleting the audit logs from the Orchestrator database as the retention period is reached. Subsequently, Orchestrator will create audit log archives once per month for the calendar month that has moved outside the most recent six-month window. For example, the logs for June 2025 are scheduled for archival at the beginning of January 2026. Once the audit logs for a calendar month have been archived, they will be removed from the Orchestrator database and will no longer be searchable.
Audit log archives are available for the 18 months that precede the most recent six-month window, ensuring that the audit log data is available to you for a total period of 24 months. Archives older than 24 months are automatically deleted.

For additional information, refer to Downloading archived data.

May 26, 2025

Improved audit logs for automatically disabled triggers

The audit log now specifies the reason for automatically disabling a trigger in the following scenarios:

The trigger was disabled upon exceeding the values defined in the tenant-level settings for Triggers - Disable when job creation fail count and Triggers - Grace period when job creation keeps failing count (days).
The trigger was disabled due to the trigger-level Set execution-based trigger disabled toggle being enabled and the values for Disable when consecutive job execution fail count and

Grace period on disabling the trigger (days) being exceeded.

Bug fixes

The tenant-level Overview page and the folder-level Home page only displayed job statistics for RPA jobs. The pages now display statistics for all job types.

May 21, 2025

Updates to outbound IP addresses

We are expanding our lists of outbound IP addresses, with the new values coming into effect from June 23, 2025 onwards. To avoid disruptions, make sure you update your firewall configuration with the newly added values before the specified date.

For the updated lists of outbound IP addresses, refer to Orchestrator outbound IP addresses.

Testing module deactivation for new tenants

Starting with this update, the majority of the Testing module in Orchestrator is deactivated for any newly created tenant. This change involves certain limitations on the Testing tab in Orchestrator, as follows:

The Test Schedules and Test Data Queues tabs are not available anymore.
However, you can still create test schedules in Test Manager, and existing test data queues on existing tenants continue to work. For more information, visit Scheduling executions in Test Manger.
The Test Executions tab now displays the Status column, instead of the Result column.
The Status column indicates the current status of the Orchestrator test execution, such as: Pending, Running, Cancelled, and Finished. Test results are visible only in Test Manager.
You cannot execute individual test cases anymore. However, you can still execute Orchestrator test sets but only using APIs (including CI/CD integrations).

For all your test data management efforts, use Test Manager.

May 19, 2025

Unified Pricing licensing model

Unified Pricing is here! Our enhanced licensing model for Orchestrator offers new plans and a flexible credit system using Platform Units. Enjoy easier tracking and reallocation of resources for Orchestrator.

Key benefits

Unified Pricing introduces the following new features:

Credit-based approach: Under Unified Pricing, all licensing consumption units - such as AI Units, App Units, Robot Units, API Calls, and Agent Units - are consolidated into a single unit, the Platform Unit. This simplification allows for easier understanding and tracking.
Enhanced flexibility: With Unified Pricing, you can easily reallocate Platform Units based on your changing project needs. Now that multiple UiPath services consume Platform Units, you are no longer constrained to pre-defined uses for the acquired units. This allows you to shift your focus and resources where your projects need them the most, whenever you require.

Who can benefit

Currently, you can acquire Unified Pricing licensing plans for Orchestrator Automation Cloud and desktop. This new licensing model caters to the needs of both existing and new customers.

If you want to continue with your existing Flex licensing model, you are free to make that choice. However, if you are currently operating under the Flex model and wish to switch to Unified Pricing, remember that this transition will require that you ensure user license management is enabled and you re-assign licenses. For more guidance, reach out to your Sales representative.

Additional resources

For comprehensive information on the user SKUs available in Unified pricing, refer to UiPath Licensing.
For guidance on how to select the optimal licensing model tailored to your needs, refer to the Overview guide.
For specifics related to the newly introduced Unified Pricing plans, user licenses, and Platform Units on the platform-level, refer to the Automation Cloud admin guide.
For licensing plans, user licenses, and their expected behavior in Orchestrator, refer to Unified Pricing licensing and Platform Units.

Time filter improvements

Note: Erratum - added May 20, 2025: Due to an oversight on our part, we originally announced this improvement on May 16, 2025. However, we enabled the improvement on May 19, 2025.

We have improved our time filters with a wider selection or predefined intervals and the addition of custom intervals.

You can now select from the following predefined intervals:

All
Last hour
Today
Last 24 hours
Last 7 days
Last 2 weeks
Last 30 days
Last 6 months

Additionally, you can select the Custom option and set the exact date and time for both the start and the end of your interval.

The improvements apply to the time filters in the following grids:

In the tenant context, under Monitoring: the Unattended Automations grid.
In the tenant context, under Audit: the Audit and Test Automation Audit grids.
In the tenant context, under Machines: the Machine Event Logs grid for a cloud robot VM pool.
In the folder context, under Automations: the Jobs and Logs grids.

Note: The improvements do not apply to the real-time monitoring pages under Monitoring.

May 14, 2025

Agents general availability

In March 2025, we announced the rollout of agents to a limited number of enterprise customers. We are now making agents generally available, allowing all our customers to leverage these advanced digital tools.

To find out more about agent capabilities and usage, refer to our initial announcement of the feature.

Introducing coded agents

We now support agents that you build using code, enabling highly tailored automations with complex logic. By developing agents in your own IDE, you have full control over agent logic, behavior and system integration.

You can use the UiPath SDK to package your coded agents as standard .nupkg packages and publish them to Orchestrator via a package feed of your choice.

Once you deploy a coded agent to an Orchestrator folder, it behaves like any standard process. Therefore, you can schedule, trigger, and monitor agent execution, as well as integrate coded agents into broader automation workflows.

Additionaly, UiPath SDKs provide logic to invoke and interact with UiPath resources directly from code: assets, queues, buckets, and more.

The following diagram provides a high-level illustration of coded agent workflows:

For more information on coded agents, refer to About coded agents.

Introducing the Secret asset type

As part of our coded agents rollout, we are making it possible to define environment variables that allow you to make configuration changes to your agent without modifying the code directly.

To assist you in providing environment variables such as API keys that your coded agent may require, we have added support for secret-type assets.

For more information, refer to About assets.

New role permissions for Agent Memory

The Agent Memory functionality that we announced in Introducing agent memory works by persisting agent execution data. This requires a new folder-level permission, Agent Memory.

The Agent Memory permission is enabled by default for the following roles and operations:

Automation Developer: View, Edit, Create.
Automation User: View, Edit, Create.
Folder Administrator: View, Edit, Create, Delete.
Personal Workspace Administrator: View, Edit, Create, Delete.

For a detailed explanation of Agent Memory, refer to Agent Memory.

For more information on role permissions, refer to Default roles.

Timeline of migration to the union of privileges model for enterprise customers

As we previously announced, we will soon begin the migration to the union of privileges model for enterprise customers that have not completed the migration themselves.

We will perform the migration according to the following timeline:

Date	Region
May 19, 2025	Enterprise customers on Community, Australia
May 20, 2025	Canada, India
May 21, 2025	United Kingdom
May 26, 2025	United States
June 3, 2025	Europe
June 4, 2025	Japan, Singapore
June 18, 2025	Delayed update organizations and Public Sector

Important:

The timelines we provide in the table are tentative and subject to change.

To exercise more control over the migration process, we strongly recommend that you perform the migration yourself, according to the instructions in Migrating from break inheritance to union of privileges.

Additionally, performing the migration yourself enables you to generate a report on the impacted users. For more information, refer to Using the migration tool.

Note that the migration tool will no longer be available after the dates specified in the table.

Improved handling of form errors

Attempting to submit a single-step form with errors now highlights the first field where an error is detected.

May 9, 2025

Introducing agent monitoring

You can now leverage agent monitoring capabilities in the tenant or folder context, by navigating to the Monitoring page, then selecting Agents.

In addition to viewing charts of live and completed instances, as well as agents with most errors, you can examine records of incidents and per-agent execution information.

For details, refer to Monitoring.

May 8, 2025

Healing Agent general availability

Healing Agent, which we introduced as a public preview feature in December 2024, is now generally available.

To find out more about Healing Agent and its capabilities, refer to the Healing Agent documentation.

May 7, 2025

Updated Folder Administrator role permissions

Note: This change became effective on March 17, 2025, but was not announced at the time due to an issue on our part.

The Folder Administrator role was missing the View, Edit, and Delete permissions for Test Case Execution Artifacts. We have fixed the issue.

May 6, 2025

Updates on mixed role migration for enterprise customers

We have successfully completed the migration of mixed roles for enterprise customers, with the exception of delayed update organizations and Public Sector. For these categories of customers, the migration will take place on May 20-21, 2025.

For more information on the migration of mixed roles, refer to our initial announcement.

Orchestrator release notes

May 2025