August 2022 - Automation Cloud latest
Orchestrator Release Notes
Last updated Dec 6, 2023

August 2022

24 August 2022

Automation CloudTM Robots - VM Machine Logs

Administrators can now diagnose and troubleshoot Automation Cloud Robots - VM machines by viewing logs generated for every machine in the pool. The log report provides relevant details about the important events happening on a machine such as machine events, job events, or Azure issues.

Viewing logs for a machine.

Search Shortcut

You can now search for resources in a tenant by using the following keyboard shortcut, which is available from anywhere within Orchestrator:

  • Ctrl + / on Windows computers
  • Cmd + / on Mac computers

Folder Names in Object Linking Pages

When you use the Link from other folders option to link an object that is already linked to several other folders, the names of these original folders are now displayed in the Folder column of the Folder validation page. Previously, the number of folders was displayed instead.

Monitoring Page Layout

The entities available on the Monitoring page are now displayed in a row instead of a drop-down list.

Asset and Queue Linking Pages - Additional Details

The Select Queue and Select Asset pages displayed when trying to link queues/assets from other folders now contain the Labels and Properties columns, allowing you to easily identify the details of each item.

Upgraded Alert Functionality

New email templates

  • Our alert emails have a fresh look. The Error summary and the Alert summary emails display information in a more intuitive and comprehensive way than they used to. Subscribe to the desired alerts and see the new emails in your inbox.

Alert root causes

  • Now each alert in the Error summary email provides a link that redirects you to the associated component page, filtered to display the root cause so you can remediate it.
  • To provide the same redirects to the root cause, we added the See alert source button to the Alerts page.

    Check out our documentation about Alerts.

Granular subscriptions

  • Filter the event types you want to receive alerts about. The enhanced Alert preferences page gives you the possibility of selecting specific events for every component that allows subscriptions. Learn how in our documentation.

Alert audience

  • As an organization administrator, you can choose the events and folders your users receive alerts about:

    • Make specific alert selections in a user alert preferences profile.
    • Restrict the folders your users receive alerts from, without removing their access in the folder.

      Find out how you can configure your user subscriptions.

New alerts for jobs

  • Jobs stuck in a pending or resumed state We know that having a job stuck in the pending or resumed state may cause some frustration. That's why we added a new toggle that activates alerts for jobs stuck in pending or resumed for a duration of your choice. Turn the toggle on to receive "Error" alerts every time the job exceeds the selected duration in the pending or resumed state, and take further actions to unblock it.

    The new toggle option is available on the Create/Edit Trigger and Start Job pages. Read the corresponding guides to find out more details (Managing triggers - step 14, Managing jobs - step 6).

  • Jobs have not finished running Seeing the running status of a job may induce enthusiasm. But seeing the same status for longer than expected may raise some questions. Don't worry, we got you covered when these things happen. A new alert will notify you of jobs that have been running for more than the configured duration. Just turn on the Generate an alert if the job started and has not completed toggle on the Create/Edit Trigger and Start Job pages. Read more details in our documentation (Managing triggers - step 15, Managing jobs - step 7).

The New Help Button in Orchestrator

  • Clicking the Helpbutton in Orchestrator now provides shortcuts to various help options, such as product-specific content - documentation, release notes, YouTube tutorials - or redirects to our support and resource centers.
  • We also renamed the feedback form link from Submit your idea to Provide product feedback.

Queue Improvements

  • The .zip file of archived queues items now contains a metadata file, which provides details about the container queue.
  • We improved queue charts by clarifying that the Business Exceptions,Application Exceptions, and Successful Transactions cards display the corresponding average execution time in seconds.

11 August 2022


For a faster web experience, Orchestrator now loads using the content delivery network (CDN).

Make sure to add the orch-cdn.uipath.com URL to your Orchestrator’s allowlist of your firewall configuration.

10 August 2022

Automation Settings Revamp for User Accounts

We revamped the administrative area where you would configure automation capabilities for user accounts. The Robot Setup tab, where admins enabled or disabled attended and unattended capabilities for a user, has been split into:

  • The Personal Automation Setup tab, previously under the umbrella of attended automation, and controlled via the Attended Robot toggle;
  • The Unattended Setup tab which, other than having its own tab, didn't undergo significant changes.



We are moving away from the term "attended" and are switching to an all-encompassing "personal automation" when it comes to user setup. Personal automation means your users are able to run processes remotely, under their own identity, in addition to locally on their machines (attended). Read on for more details about personal remote automation.

Personal Remote Automations

Unattended automations typically run on robot accounts, the UiPath equivalent of Windows service accounts. An administrator can enable an unattended robot to impersonate a user account; that is, act on behalf of that user identity, to allow the robot to run automations with the same privileges as the user it impersonates.

Running unattended automations on user accounts is typically needed by RPA developers debugging their automation projects, as well as citizen developers and business users running automations under their own identity, but on server-side resources instead of their local machines.

Until now, running an automation as yourself on remote machines, required an admin to first configure your account to allow impersonation by an unattended robot by enabling the Unattended robot toggle.

Starting today, both developers and business users can run background automation under their own identity on remote machines via personal automation capabilities; without requiring an unattended robot configured for their user accounts. We call these personal remote automations, since they run under the user's identity and on server-side resources to which the user has no direct access.

Starting a job manually from Orchestrator to run as yourself

Configuring a time trigger in Orchestrator to run as yourself

Note: When a Named User license is removed from a user, their personal robot is removed, and any trigger running under that user's identity (set to Run as myself) becomes invalid. Reallocating a license to the user does not revalidate the trigger. You need to delete the broken trigger, and create a new one.

Allocating host machines for personal remote automation is done using machine templates. An Orchestrator administrator configures and sets up the remote infrastructure for users by adding a machine template object to the users' folders, just as they would do in a typical unattended setup. It can be a machine template, an Elastic Robot Pool, a Cloud Robot - VM, or a Cloud Robot - Serverless machine.

You can still enable unattended automation on user accounts in addition to personal remote automation. The differences between the two being that:

  • You can only run personal remote automations if the underlying process is a background process; it does not work for processes that require user interaction. To execute processes that require user interaction, configuring an unattended robot is still required. Learn how to enable users to run automation on unattended infrastructure via unattended robots.
  • In personal remote automation, the user's identity is used for executing that single process, so it helps achieve granular control in terms of when and how the user's identity is used. Unattended robots, on the other hand, act as the user they impersonate to execute processes across all folders the user has access to.

Admins: Learn how to enable your users to run personal automations.

Developers and business users: Learn how to run personal remote automation.

Robot Settings Interface Changes

The following changes have been made to the Robot Settings page:

  • The Resolution settings section has been renamed to Session settings.
  • The Login To Console option has been moved from the Logging settings section to the Session settings section.


The external application ID now shows up in the audit grid of your queue item events.

Bug Fixes

Enabling and disabling Test Schedules several times triggered unexpected job executions. This issue has been addressed.

When Can I See These Changes?

The date when a change is first announced in the release notes is the date when it first becomes available.

If you don't see the change yet, you can expect to see it soon, after we roll out changes to all the regions.

More information

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2023 UiPath. All rights reserved.