orchestrator
latest
false
  • Release notes
      • September 2025
      • August 2025
      • July 2025
      • June 2025
      • May 2025
      • April 2025
UiPath logo, featuring letters U and I in white

Orchestrator release notes

Last updated Sep 29, 2025

September 2025

September 29, 2025

Environment variables values masking

When environment variables are passed as raw strings to a process or job, only the variable key is now returned. This prevents sensitive values from being exposed. The behavior is consistent with credential assets, where passwords are also masked.

Linking execution settings for Process packages

You can now bind execution settings directly to packages of type Process. This allows you to define runtime type, account, and machine requirements at the package level, ensuring processes run in the right environment.

For more information, check the Managing packages requirements page.

Notification when disabling SignalR

A new warning message is now displayed when disabling SignalR from the Scalability menu in Tenant Settings. This message informs you that disabling SignalR on the tenant can lead to some UiPath capabilities, including Studio Web, to function improperly or stop working altogether.

September 12, 2025

New credentials store integration: Google Secret Manager

We added support for Google Secret Manager as a credential store in Orchestrator. There are two plugins included with the integration:
  • Google Secret Manager - a read-write plugin that allows you to create and manage secrets directly from Orchestrator.
  • Google Secret Manager (read-only) - a read-only plugin that only allows you to consume existing secrets. Secrets must be provisioned directly in Google Secret Manager.

This integration provides secure credential management, centralized storage, and support for assets and unattended robot passwords.

September 9, 2025

Trigger history

You can now track the instances when the trigger failed to start jobs from the new History tab. This feature helps you better understand and troubleshoot trigger behavior.

For more information, check the Trigger details page.

Default Robot account

As part of the organization creation flow, a new robot account, Default Robot, is now automatically added to all newly created organizations.

The account is included in the Automation Users group and is provisioned in all tenants of the new organization. Within each tenant, it is assigned to the auto-created Shared Folder with the Automation User role.

This setup provides out-of-the-box Unattended automation support for new organizations and their tenants.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2025 UiPath. All rights reserved.