# June 2026 > When starting a Windows (foreground) automation job, the default execution account is now **Any** instead of **Run as Myself (Personal automation)**. ## June 30, 2026 ### Default execution account updated for Windows (foreground) automations When starting a Windows (foreground) automation job, the default execution account is now **Any** instead of **Run as Myself (Personal automation)**. ## June 25, 2026 ### Updated layout for the Start Job page The **Start Job** page now appears in a card layout with shadow and rounded corners, replacing the previous flat layout. Spacing between the form content and the action buttons is consistent, and the breadcrumb bar is now sticky so it stays visible as you scroll through longer forms. ![Start a job page before and after updated layout](https://dev-assets.cms.uipath.com/assets/images/orchestrator/Start-a-job-new-layout-8eb4580c.webp) ## June 22, 2026 ### Jobs tab on the Solution deployments side panel :::note **Correction**: This feature was released on June 25, 2026. ::: When you select a solution from **Registry** > **Solution deployments** or **Solutions** > **Deployments**, the details panel now includes a **Jobs** tab. The tab shows the last 50 jobs started in the last 24 hours associated with the selected deployment, giving you direct visibility into job activity without leaving the current page. Selecting a job opens the Job Details sidepanel. The **Explore all** link opens the jobs page in Orchestrator. ### Inline chip filters on the Processes Registry and Resources pages The **Processes Registry** and **Resources** pages now include inline chip filters for columns with a fixed set of values, such as Type and Entity Type. Instead of expanding a dropdown, you can select a chip directly in the filter row to filter the grid in one step. An **All** chip clears the active filter. When options don't fit the filter row, the overflow is grouped under an **Other** chip that opens a menu. ![Processes registry filter chips](https://dev-assets.cms.uipath.com/assets/images/orchestrator/Processes-registry-filter-chips-eb567831.webp) ### Deprecation announcements for API The following `/odata/Robots` API endpoints are tightly coupled with classic folders and are being fully deprecated: - `GetById` - `Create` - `Update` - `PartialUpdate` - `Delete` - `DeleteBulk` - `ConvertToFloating` - `GetMachineNameToLicenseKeyMappings` - `GetUsernames` - `ToggleEnabledStatus` ### Maestro process type labels updated The display labels for the three Maestro process types have been renamed to align with the current Maestro branding: | Previous label | New label | |---|---| | Agentic process | Maestro BPMN | | Case Management | Maestro Case | | Flow | Maestro Flow | The new labels appear in type filters, column values, and package dropdowns throughout Orchestrator, including the Processes Registry, the Jobs grid, and process deployment screens. ### Updated layout for create and edit forms Create and edit forms across Orchestrator now appear in a card layout with shadow and rounded corners, replacing the previous flat layout. Spacing between form content and action buttons is consistent, and the breadcrumb bar is now sticky so it stays visible as you scroll through longer forms. ![Orchestrator create and edit form pages before and after the layout update](https://dev-assets.cms.uipath.com/assets/images/orchestrator/New-Layout-848b1cc7.webp) ### Bug fixes * We fixed an issue preventing queue item recordings from being visible and accessible from linked folders for shared queues. We updated recording authorization and lookup logic to support access to recordings through shared queue links across folders. * We fixed an issue where deleting a folder that contained non-final jobs (Pending, Resumed, Running, Stopping, Suspended, or Terminating) never completed. The folder cleanup process now correctly identifies and stops non-final jobs, allowing folder deletion to complete as expected. * We fixed an issue where upgrading a solution containing a process that referenced a deleted retention bucket failed mid-install with a "Bucket does not exist" error. Solution deployment validation now checks that referenced retention buckets exist and surfaces a clear error before the install phase begins. * We fixed an accessibility issue in the folder tree view where the **Actions** and **Folder management** menu sections were not programmatically associated with their group labels. Screen readers now correctly announce the section context when users navigate folder menu items. ## June 8, 2026 ### Navigate to a folder from the cross-folder Jobs grid The all-jobs cross-folder grid now includes a **Go to folder** inline action on each row. Selecting it opens the **Jobs** page for that row's folder. When the job has an associated release, the page is pre-filtered by the job's process. For more information, check [Jobs](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/jobs-monitoring). ![Go to folder button](https://dev-assets.cms.uipath.com/assets/images/orchestrator/Go_to_Folder-ba33d0fa.webp) ### Run as Myself renamed and extended to Windows automations When you configure an execution target through bindings, the **Run as Myself** option is now labeled **Inherit parent job identity**, making it clearer that the invoked job runs under the identity of the parent job. This option is now also available for Windows (foreground) automations, not only background processes. When you use it for a Windows automation, the parent job identity must have an unattended robot with credentials configured — otherwise the invoked job fails to start. For more information, check [About jobs](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-jobs). ### Out-of-the-box execution identity for new folders You can now configure a tenant-level default execution identity—a default account and machine—that is automatically applied to new folders as they are created. This removes much of the manual setup previously required before you could run automations in a newly created folder. New tenants are provisioned with an out-of-the-box default configuration, and administrators can review and update the tenant's default execution identity at any time. For more information, see [Default Execution Identity](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-default-execution-identity) and [Configure the Default Execution Identity](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configure-default-execution-identity). ### Automatic cleanup of Default Execution Identity references When a user or machine is deleted from a tenant, the references to that user or machine are now automatically removed from the tenant-level **Default Execution Identity** configuration. Previously, deleted users or machines remained as dangling entries in the configuration. The references were skipped at apply time, but they produced repeated warning logs and made the configuration harder to inspect. With this change, the configuration stays in sync with the actual users and machines in the tenant. ### Unified outbound IP ranges — transition begins Orchestrator outbound IP ranges are being unified. The new unified outbound IP ranges apply per regions (for example, United States, Europe, etc.) and are the same for all UiPath services within a region. For the full list of affected services, refer to the [June 8, 2026 Automation Cloud release notes](https://docs.uipath.com/automation-cloud/automation-cloud/latest/release-notes/june-2026#june-8%2C-2026). The current Orchestrator outbound IP ranges will remain active until September 16, 2026. Starting September 16, they will be progressively phased out as the unified IP ranges take effect. **What you need to do**: 1. **Add the new unified IP ranges to your firewall configuration now.** Find the full list of unified outbound IP ranges by region on the [Configuring the firewall for Automation Cloud](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud) page. 2. **Until September 16, 2026**: Keep both the current Orchestrator outbound IP ranges (on the [Legacy - Configuring the firewall for Automation Cloud](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud-legacy#orchestrator) page) and the new unified IP ranges allowlisted simultaneously. 3. **After September 16, 2026**: Continue allowlisting both sets of IP ranges until a subsequent release note confirms the legacy IP ranges can be safely removed. ## June 2, 2026 ### South Korea region support for Orchestrator As part of our ongoing cloud expansion, we're bringing complete data sovereignty to the South Korea region for Orchestrator, ACR - VM, and ACR - Serverless. This ensures your data is securely stored and replicated across multiple availability zones within South Korea, offering full control and compliance confidence. For more information, refer to the [Global cloud regions](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/global-cloud-regions) page.