# November 2023

> November 2023 release notes for Orchestrator in Automation Cloud.

## 30 November 2023

### Editing the details of a deployed app

Now you can easily update the details of a deployed app, including the app name, description, or version. Simply navigate to the Orchestrator folder where the app was deployed, open the **Automations** > **Apps** page, access the **More actions** menu for the desired app, click **Edit app details**, and make the necessary changes with ease.

## 28 November 2023

### Auditing machine maintenance actions

The **Audit Data** window for the **Sessions** component now includes the **Maintenance** field, which displays the status of the **[Maintenance](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/monitoring-unattended-sessions)** option for unattended machines. 1 marks the enabled status of the machine maintenance mode, and 0 marks its disabled status.

### Support for S3 buckets with SSE-KMS

Orchestrator now supports server-side encryption with AWS Key Management Service keys (SSE-KMS) for Amazon S3 storage buckets.

### New limits on transaction details

We are enforcing the following maximum limits on transaction details fields, in an effort to prevent system overload:

* Specific data - 1 MB
* Output data - 1 MB
* Analytics data - 1 MB
* Exception reason - 524,288 characters
* Exception details - 524,288 characters

### Performance improvements

The performance of fetching items from folders with large numbers of assets has been improved.

## 13 November 2023

### Running jobs via API calls

Orchestrator now provides you with a streamlined way of executing jobs through a third-party application of your choice.

To that end, we are introducing API triggers, a means to generate an API endpoint that allows you to run a job from an external application. All you need to do is create a trigger based on a process, copy the resulting URL, paste it into your tool, and authorize the request - this will run the job with the parameters you define.

These are the new items that you'll notice in the interface as part of this launch:

* the **API Triggers** option in the **Automations** > **Triggers** section
* the **API Trigger** option in the **Add Trigger** list of the process contextual menu
* several tenant settings to be found on the **General** tab:
  + **CORS allow list for API triggers** (in the **API Settings** section)
  + **Require Authentication header for sync API Triggers redirects** (in the **API Settings** section)
  + **Triggers - API Triggers - Maximum pending jobs limit** (in the **Execution settings** section)

Find out more [general information](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/api-triggers) about API triggers, learn how to [manage](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-api-triggers) them, then see how to [run](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-jobs#starting-a-job%23starting-a-job-through-an-api-trigger) a job via an API trigger.

### Authenticating external feeds

External feeds used for libraries can now also be secured through basic authentication credentials, as is already the case for packages.

### Re-triggering queue triggers

We are upping the effectiveness of our queue triggering system with a new option: **After completing jobs, reassess conditions and start new jobs if possible**. When selected, the queue trigger is evaluated after each job completion, aiming to identify any resources that could be put towards processing remaining queue items.

This prevents the inefficient use of our infrastructure, as it ensures that there are no idle robots and stagnant queued items simultaneously.

![Screenshot of the After completing jobs, reassess conditions and start new jobs if possible checkbox](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-after-completing-jobs-reassess-conditions-and-start-new-jobs-if-possible-checkbox-333562-0e03ae77-870d8d60.webp)

### Checking assigned roles and permissions

Our mission of optimizing the access control framework continues with a significant improvement to the roles and permissions check window.

Up until now, all tenant and folder roles were bundled in one list, without details on permissions. Now, you not only have access to more information, but you also benefit from a friendlier view: roles are displayed in separate tenant and folder categories, all permissions included in each granted role are visible at a glance, and filtering by role or folder allows you to focus on the precise details that are of interest to you.

![Comparison between Tenant access interfaces](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-comparison-between-tenant-access-interfaces-333780-79419471-1ec47197.webp)

### Directory user events handling in Orchestrator

Now, any changes made to your directory users in the **Admin** portal - including updates or deletions - are reflected within your Orchestrator's user list and audit logs across all tenants.

In more detail, Orchestrator now logs the updates or deletions under the following descriptor: `User System Administrator updated/deleted account {user_mail}`. For a full breakdown of the changes, click **View Details** in **Audit Data**.

When a directory user is deleted:

1. Any connected robots will also be automatically deleted.
2. Associated personal workspaces will become orphaned. These can still be explored, or you can choose to convert them into modern folders.

Please note, a delay may be experienced whilst synchronizing these updates to Orchestrator.

### Decreasing the storage limit for input/output arguments

The storage limit for input/output arguments is currently 1 MB for **Free** and **Community** customers, and 30 MB for **Enterprise** customers. However, we are now rolling out the 1 MB limit to **Enterprise** as well, to be enforced soon.