- Automation Cloud and Test Cloud
- Automation Cloud Public Sector and Test Cloud Public Sector
- Automation Cloud Dedicated
August 2026 release notes for Orchestrator in Automation Cloud Public Sector.
August 3, 2026
Process link in job sidepanel
When monitoring jobs, you can now access the parent process directly from the job sidepanel header. Selecting the process link displays the process details within the sidepanel (replacing the job sidepanel), improving navigation efficiency during troubleshooting and monitoring.
Triggers now support creating in a disabled state
When creating a trigger, you can now optionally disable it at creation time. By default, triggers are enabled and start processing items immediately. You can disable a trigger during creation to complete configuration and testing before activating it. This applies to all trigger types: queue, event, and time triggers.
Serverless machine auto-assignment
When a tenant is provisioned with a serverless machine, the machine is now automatically assigned to the default modern folder. Previously, the serverless machine was provisioned but required manual assignment to a folder.
For more information, check About Machines.
Improved sidepanel job grid filters
The job grid displayed in the sidepanel context now hides process-type filters (Type and User interaction) that are not applicable in that context. These filters remain visible in the full jobs grid where they provide value.
For more information on jobs filtering, check the Jobs monitoring page.
Bug fixes
-
We fixed an issue where webhook secrets were displayed in plain text in the user interface. Webhook secrets are now hidden by default, similar to other sensitive credential fields. For more information, check About Webhooks.
-
We fixed an accessibility issue in the tenant quick actions submenu. Menu items are now navigable using Arrow keys only when a screen reader is active, eliminating the need for mixed Tab and Arrow key combinations.
-
We fixed an issue where some package upload events contained corrupted event data with default key values (00000000-0000-0000-0000-000000000000). Event data validation has been improved to prevent malformed events from being recorded.