# July 2026 > July 2026 release notes for Orchestrator in Automation Cloud. ## July 31, 2026 ### Correction to Serverless UiPath Outbound IP Ranges guidance We corrected the [UiPath Outbound IP Ranges](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/outbound-ip-ranges) page to clarify that Automation Cloud Robots - Serverless are not part of the transition to unified UiPath Outbound IP Ranges. The service-specific UiPath Outbound IP Ranges listed on that page remain applicable. ## July 30, 2026 ### MCP OAuth flow now in public preview UiPath MCP Servers now include a built-in OAuth proxy that enables any MCP client implementing the [MCP Authorization specification](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization) to authenticate automatically, without manual token management. When connecting for the first time, the MCP client opens a browser window where you log in to UiPath. After logging in, a consent page displays the MCP client's name, the scopes it is requesting, and a list of the tenants you have access to. You select the tenant you want to authorize for and approve the connection. The MCP Server then becomes available in the client, and the selected tenant is remembered for future sessions. This is a public preview release. VS Code with GitHub Copilot is fully supported. The OAuth proxy includes the following capabilities: * **Resource Indicators (RFC 8707)**: MCP OAuth sessions are bound to the specific MCP server they were authorized for. A token issued for one server is rejected by other servers, providing an additional security boundary. Clients that don't yet support resource binding (such as Microsoft Copilot) fall back gracefully to tenant-scoped sessions. * **Client ID Metadata Documents (CIMD)**: in addition to Dynamic Client Registration (DCR), UiPath supports CIMD as a registration-free client identification method. CIMD allows clients to identify themselves using an HTTPS URL pointing to a publicly accessible metadata document, making it the emerging standard in the MCP ecosystem. * **Per-organization callback-domain allow list**: organizations can restrict which callback domains are authorized to receive OAuth authorization codes. This provides administrators with fine-grained control over where authorization codes can be delivered, complementing the existing governance policies. For setup instructions, check the [Authenticating with the MCP OAuth flow](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/authenticating-with-the-mcp-oauth-flow) page. ## July 28, 2026 ### Consumption field hidden from job details The Consumption field has been removed from the job details sidepanel. Consumption values were calculated asynchronously and could be inaccurate. This field will be restored once accurate consumption reporting is in place. ## July 24, 2026 ### Serverless Automation Cloud Robots support for Relay Coded processes running on Serverless Automation Cloud Robots can now call on-premises APIs through Relay. The process sends requests to the registered endpoint's Mapped URL and uses an access token that the robot runtime injects automatically. Only HTTP-based connections are supported through Relay. Database Hub connections over Relay are not yet supported. For details, see [Calling on-premises APIs via Relay](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/calling-on-premises-apis-via-relay). ## July 23, 2026 ### Queue triggers now support Maestro processes Maestro processes can now be triggered by Orchestrator Queue Items, enabling queue-driven workflows in Maestro. When a new item is added to a queue, a Maestro process instantly starts to process it. Each queue item triggers exactly one Maestro process instance. Maestro processes can manage the queue item lifecycle using queue operations activities (add, delete, set status, postpone items). For more information, check [Queue Triggers](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/queue-triggers). ## July 21, 2026 **Correction, July 22, 2026**: We removed the entry for the **Python and JavaScript process feeds** as it was not released as scheduled. ### 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. ![Enable trigger button highlighted in the Orchestrator UI](https://dev-assets.cms.uipath.com/assets/images/orchestrator/Enable-trigger-5b065763.webp) ### 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](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/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](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/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](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/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 accessibility issue in the agent context sidepanel where the resize separator was not keyboard operable. The separator is now properly focusable and can be manipulated using keyboard navigation. * 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. ## July 8, 2026 ### Bug fixes * We fixed an issue where custom user settings were not applied when a process was triggered by a disconnected Event Trigger. Previously, the job would attempt to use the developer's design-time connection instead of the runtime user's configured connection, causing permission errors. Custom user settings are now properly resolved when processes are executed via Event Triggers. ## July 6, 2026 ### Bulk edit queue items You can now update multiple queue items at the same time from the Transactions grid. Select one or more items and apply bulk changes to the following fields: * Priority * Postpone date * Due date * Reset transaction progress For more information, check [About Queues and Transactions](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-queues-and-transactions). ### Processing Exceptions encrypted for new encrypted queues When you create an encrypted queue, Orchestrator now also encrypts **Processing Exceptions** in the database. Previously, only **Specific Data** and **Output** were encrypted. This change applies only to queues created after this release. Existing encrypted queues are unaffected. :::note If you have Insights dashboards displaying **Processing Exceptions** from encrypted queues, new queues will display encrypted text in those dashboards. ::: For more information, check [Managing Queues in Orchestrator](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-queues-in-orchestrator). ### Extended search when assigning per-account asset values When configuring per-account values for an asset, you can now search for accounts by name. Previously, you had to scroll through a static list to find a specific account. The search queries the identity service directly, so all accounts in the tenant are findable regardless of the list size. For more information, check [About Assets](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-assets). ### Entry point preserved when updating a process version When you edit a process and change the package version, Orchestrator now retains the previously selected entry point if that workflow still exists in the new version. Previously, changing the package version reset the entry point to the Main file, requiring you to reselect it manually. For more information, check [About Processes](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-processes). ### Update available icon now triggers an upgrade In the Processes grid, selecting the **Update available** icon next to a process version now opens the upgrade confirmation dialog and updates the process to the latest package version. Previously, selecting the icon opened the process requirements sidepanel. For more information, check [About Processes](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-processes). ### Video recording API endpoints now public Four API endpoints for downloading and deleting execution video recordings are now publicly available in Swagger. Use these endpoints to retrieve time-limited download URLs for a job's or queue item's recordings, or to delete recordings programmatically: - `GET /api/VideoRecording/jobs/{jobKey}/read` - `DELETE /api/VideoRecording/jobs/{jobKey}` - `GET /api/VideoRecording/QueueItems/{queueItemId}/Read` - `DELETE /api/VideoRecording/QueueItems/{queueItemId}` Read operations require `Jobs.View` and `ExecutionMedia.View` permissions. Delete operations require `Jobs.Delete` or `Queues.Delete` and `ExecutionMedia.Delete`. The OAuth scope is `Monitoring`. For more information, check [Video recordings requests](https://docs.uipath.com/orchestrator/automation-cloud/latest/api-guide/video-recordings-requests). ### Environment-related permissions deprecated The permissions associated with Environments are deprecated and will be removed in a future release. If your roles include Environment permissions, review and update them before the removal. ### Bug fixes * We fixed an issue where queue items linked to suspended Maestro jobs were incorrectly abandoned. Maestro uses a suspension path that does not set the `ResumeVersion` column, which caused Orchestrator to treat those jobs as non-resumable and abandon their queue items. Queue items now remain in their current state when a Maestro job is suspended. * We fixed an accessibility issue where the tenant quick actions submenu required a mixed combination of Tab and Arrow keys to navigate when using a screen reader. Menu items within the submenu are now navigable using Arrow keys only.