Orchestrator release notes
Release date: September 9, 2025
We added a configuration option to forward requests to active nodes in case of consistency issues with a HashiCorp Vault setup.
<add key="Plugins.SecureStores.HashiCorp Vault.ForwardToActiveNode" value="true"/>
<add key="Plugins.SecureStores.HashiCorp Vault (read only).ForwardToActiveNode" value="true"/><add key="Plugins.SecureStores.HashiCorp Vault.ForwardToActiveNode" value="true"/>
<add key="Plugins.SecureStores.HashiCorp Vault (read only).ForwardToActiveNode" value="true"/>X-Vault-Forward: active-node header is set for all
requests sent to your HashiCorp Vault credential store.
We added support for the LDAP option under the Secrets Engine configuration in HashiCorp Vault credential stores within Automation Suite, aligning with the functionality already available in Automation Cloud™.
On the tenant-level Monitoring screen, under Unattended sessions, you can now display the running, stopping and terminating jobs for each machine. For more information, refer to Unattended sessions.
We added support for Windows Server 2025.
- We have fixed an issue in Jobs where selecting the Export button after
entering a value in the search box resulted in an
Invalid OData query options (#1000)error. - We have fixed an issue where webhooks failed to start after encrypting the
appsettings.Production.jsonfile, causing the application to fail on startup. - We have fixed an issue where API calls to retrieve queue-item comments and events from the Orchestrator API were not being processed correctly in cross-folder scenarios. The issue no longer occurs.
- We have fixed an issue where using the OpenLDAP data store for HashiCorp Vault caused an exception to be thrown.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
You can download the latest product version from the Customer Portal.
