# Version 141856

**A new release of Sherpa Orchestrator has been released: Version 141856.**

1. The API reference in the Orchestrator interface has been redesigned. Now, when creating and modifying entities, you can specify both ID and GUID for related objects.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-9301e7e7e2e6c97b7cd6bbd5b9133660388e259f%2Funknown%20(32).png?alt=media" alt=""><figcaption></figcaption></figure>

2. A new parameter `session_last_activity_timeout` has been added to the application configuration file backend/config/config.ini, which allows you to set the session lifetime during inactivity (after the last page update by the user), in minutes. The default value is 30 minutes.
3. A preconfigured Dashboard with system metrics of the Orchestrator has been created on the “Overview” screen, allowing you to track changes in system status - memory usage, free disk space, etc.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-e3ba0da7ae74953ce0f2bd8bc3da36d0abe8e88d%2Funknown%20(62).png?alt=media" alt=""><figcaption></figcaption></figure>

4. When creating a Job, the ability to select a priority (priority) has been added: 1 — Low, 2 — Normal, 3 — High, which allows you to manage the execution order of Jobs.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-c22062f1c0bdb25b01bf2eb649663aabbee35573%2Funknown%20(33).png?alt=media" alt=""><figcaption></figcaption></figure>

If there are multiple jobs in the Job list that have different priorities and are assigned to the same Robot (or without assigned Robots), those with a higher priority will be executed first.

5. On the Triggers screen, when creating and editing a Trigger on the "Main" tab, an option to set the priority of Jobs created by the Trigger has appeared, with the choice: 1 — Low, 2 — Normal, 3 — High, which provides more flexible management of automations controlled by Triggers.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-722ebf070ce95ea6e238aac946cd95c625728cf3%2Funknown%20(34).png?alt=media" alt=""><figcaption></figcaption></figure>

6. On the "Queues" screen, when viewing a specific Queue, the average processing time of Tasks in the Queue (per hour/per day) has been added, which helps better assess the performance of Queues.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-eaa922daa44d1dd793d48c640abee58e55bab355%2Funknown%20(35).png?alt=media" alt=""><figcaption></figcaption></figure>

7. On the "Actions" screen, when editing and creating actions on the "Action Buttons" tab, if the "Add new task" checkbox is selected, the ability to set a prefix for the name of the created task has been added - in the "Name of the created task" field. The task will be created with the actual name in the format: “Selected\_name - creation\_date\_time”.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-63e647aeb6217187e2164d6d6cb0b76e30897a26%2Funknown%20(36).png?alt=media" alt=""><figcaption></figcaption></figure>

8. Also, on the "Actions" screen, when editing and creating actions on the "Action Buttons" tab, if the "Add new task" checkbox is selected, an option to set parameters for the current task has been added: to set the name for the new task with the value selected in the "Take the name of the created task from the current task parameter" field. The user can enter the name of the task parameter from which the name will be automatically pulled.
9. On the “Triggers” screen, when editing and creating a Trigger, tags are now loaded only after selecting a Queue, which improves the performance of the window.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-b9e1f188c1a0b1c01923fc03f39b78304026d121%2Funknown%20(37).png?alt=media" alt=""><figcaption></figcaption></figure>

10. Additionally, multiple minor improvements have been implemented to enhance the stability of the Orchestrator and current known issues in the system have been fixed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sherparpa.ru/en/obnovleniya/obnovleniya-sherpa-orchestrator/versiya-141856.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
