- Automation Cloud and Test Cloud
- Automation Cloud Public Sector and Test Cloud Public Sector
- Automation Cloud Dedicated
November 2026
November 2026 release notes for Orchestrator in Automation Cloud.
November 10, 2026
Upcoming change to how jobs use process and user values
In an upcoming release, Orchestrator will change how it chooses the value a job uses for each resource, such as a connection. The value a job uses will depend only on whether the resource is set on the process or Configurable by users:
- Set on the process: every job will use the process value, no matter who runs the job or how the job is started.
- Configurable by users: each job will use the value of the user whose robot runs the job. Users set their values on the Custom user configurations page.
- Event triggers: if the connection is set on the process, only the process trigger will start jobs. If the connection is Configurable by users, only the users' triggers will start jobs.
If a resource is not set on the process and the user has no value, the job still uses the value from the package.
Until this change is enabled, jobs started with a specific robot or by a user's event trigger use the user's value, even when the value is set on the process. Jobs started with dynamic allocation do not use user values. For details about resource configuration, see Managing package requirements.
Access policies for automation resources (Public Preview)
Access policies are now released in Public Preview.
Access policies can now govern Orchestrator processes. An access policy defines which automation processes can invoke a given resource within a tenant. Policies provide an additional layer of security on top of existing role-based access control by evaluating process-to-process invocations against a central policy engine.
Access policies can protect the following resource types:
- Agent
- Maestro BPMN
- RPA Workflow
- API Workflow
- Maestro Case
- Maestro Flow
Policies target resources and calling processes by type and, optionally, by tags already applied to your Orchestrator resources. You can require matching any, all, or none of the specified tag values. You can also restrict the actor by specific users, groups, or robots.
To validate a policy before enabling it in production, use Simulation Mode, which evaluates invocations and logs the results as traces without blocking them.
Organization administrators and users with the Authorization/Access policy permission create and manage access policies in Admin > Access policies > Policies.
For more information, see About access policies and Managing access policies.
November 9, 2026
Deployments, Processes, and Resources in the new layout sidebar
In the new Orchestrator layout, Deployments, Processes, and Resources are now separate items in the sidebar. Previously, these pages were tabs of the Deployments registry group, with Deployments named Solution deployments. The classic layout is unchanged.
For details, see About the new Orchestrator layout and New layout navigation map.
Solution packages from multiple feeds
Orchestrator now supports listing solution packages and their versions from multiple feeds: the tenant feed, a single folder feed, multiple folder feeds, or all folder feeds. Each listed package includes its folder path and feed. You can filter the list by feed, or exclude a feed from the results, and sort it by name, version, or publish date.
For details about feeds, see Solution feed.
Sorting time triggers by next run time
You can now sort the time triggers list by the Next Run Time columns, both relative and absolute. Triggers without a next run time, such as disabled triggers, are always listed last.
Time zones for British Columbia, Alberta, and Manitoba
British Columbia, Alberta, and Manitoba stop changing their clocks on November 1, 2026. To support this change, you can now select the following time zones for triggers:
- (UTC-07:00) Pacific Time (British Columbia)
- (UTC-06:00) Mountain Time (Alberta)
- (UTC-05:00) Manitoba
Triggers that use the Pacific, Mountain, or Central time zones still change clocks, so after November 1, 2026 they run one hour off local time in these provinces. To keep them on local time, switch them to the new time zones. For details, see Time triggers.
Machine key authentication deprecation warnings
Machine key authentication will be deprecated. To help you prepare, Orchestrator now warns you about robots that still use it:
- On the Robot security tab of the tenant settings, a deprecation warning is displayed while Hybrid is selected for unattended or attended robot authentication.
- A Machine key authentication deprecated alert is sent for each standard machine that still connects with a machine key only.
Switch your unattended robots to client credentials and your attended robots to interactive sign-in. For details, see Robot authentication.
Overlap check for the serverless VPN address space
When you save a serverless robot machine template with VPN integration enabled, the address space is now checked against your existing network ranges. If the address space overlaps with an existing range, the template is not saved and an error is displayed. Previously, the overlap was detected only later, by the background VPN synchronization, and reported as a generic notification.
For details, see Executing unattended automations with serverless robots.
Bug fixes
- We fixed an issue where duplicating a job also required the View permission on Robots. Duplicating a job now requires only the Create permission on Jobs and the View permission on Processes. For details, see Duplicating a job.
November 2, 2026
Bug fixes
- We fixed an issue where
job.createdwebhook events sent theStartInfo.SourceandJobs[].SourceTypefields as numbers instead of names for most job sources, such as API triggers. These fields now always contain names. If your integration expects numbers, update it. For details, see Types of events.
- November 10, 2026
- Upcoming change to how jobs use process and user values
- Access policies for automation resources (Public Preview)
- November 9, 2026
- Deployments, Processes, and Resources in the new layout sidebar
- Solution packages from multiple feeds
- Sorting time triggers by next run time
- Time zones for British Columbia, Alberta, and Manitoba
- Machine key authentication deprecation warnings
- Overlap check for the serverless VPN address space
- Bug fixes
- November 2, 2026
- Bug fixes