# Queues

**Queues** are a way to group similar Tasks and create streams of Tasks.

Queues can be viewed as a way of "storing a list of data" that needs to be processed. Such groupings are used so that an external system (or Robots) can add Tasks to the Queue, while other Robots execute the items in the Task Queue, meaning they extract Tasks from a specific Queue and perform Works. Thus, a long and complex business process can be broken down into a set of simple processes, each of which will be executed by a specific Robot or Group of robots.

Tasks can be added to the Queue in three ways:

* manually by the User using the Orchestrator;
* by a Robot using the "Add Task to Queue" block;
* via API calls.

The "Queues" screen contains two tables: "Queues" and "Tasks".

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

To work with Queues, the following buttons are available on the screen:

<table><thead><tr><th width="222.111083984375"></th><th width="482.888916015625"></th></tr></thead><tbody><tr><td><strong>Button Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Create</td><td>Allows the User to create a new Queue. When clicked, a form opens for entering the necessary data and configuring the parameters of the new Queue.</td></tr><tr><td>Update</td><td>Allows updating information about the selected Queue.</td></tr><tr><td>Delete Selected</td><td>Allows deleting one or more selected Queues.</td></tr><tr><td>Import from CSV</td><td>Allows the User to upload Queue data from a CSV file. When this option is selected, a dialog box opens for uploading the file with the necessary data.</td></tr><tr><td>Export to CSV</td><td>Allows saving information about Queues to a CSV file.</td></tr><tr><td>Export to XLSX</td><td>Allows exporting Queue data to an XLSX file.</td></tr></tbody></table>

To work with Tasks, the following buttons are available on the screen:

<table data-header-hidden><thead><tr><th width="219.55560302734375"></th><th width="484.2222900390625"></th></tr></thead><tbody><tr><td><strong>Button Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Create</td><td>Allows the User to create a new Task. When clicked, a form opens for entering the necessary data and configuring the parameters of the new Task.</td></tr><tr><td>Update</td><td>Allows updating information about the selected Task.</td></tr><tr><td>Change Status</td><td><p>Allows changing the status of one or more selected Tasks. Possible options:</p><ul><li>Created;</li><li>In Progress;</li><li>Successful;</li><li>Failed;</li><li>Deferred until;</li><li>Abandoned.</li></ul></td></tr><tr><td>Clone Task</td><td>Allows creating a copy of the selected Task with automatic transfer of all its properties and parameters.</td></tr><tr><td>Delete Selected</td><td>Allows deleting one or more selected Tasks.</td></tr><tr><td>Import from CSV</td><td>Allows the User to upload Task data from a CSV file. When this option is selected, a dialog box opens for uploading the file with the necessary data.</td></tr><tr><td>Export to CSV</td><td>Allows saving information about Tasks to a CSV file.</td></tr><tr><td>Export to XLSX</td><td>Allows exporting Task data to an XLSX file.</td></tr><tr><td>Show Chart</td><td>Allows visualizing Task data in the form of a chart for analyzing Task statuses.</td></tr></tbody></table>

## **Creating a New Queue**

To create a new Queue, you need to click the "Create" button in the "Queues" table and fill out the opened form:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-7e8fc8be9fa1f5afbb7ed64963f9d445a2199abf%2F2025-04-19_21-16-34.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="57"></th><th width="283.22222900390625"></th><th width="380.77783203125"></th></tr></thead><tbody><tr><td><strong>#</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>Text field "Name"</td><td>Name of the Queue. A required field.</td></tr><tr><td>2.</td><td>Text field "Description"</td><td>Description of the Queue.</td></tr><tr><td>3.</td><td>Text field "Access Folder"</td><td>Allows specifying the Access Folder for the created Queue.</td></tr><tr><td>4.</td><td>Text field "Change status to 'Abandoned' for tasks in 'Created' status after the specified number of minutes"</td><td>Allows specifying the number of minutes after which a Task in <strong>Created</strong> status will be changed to <strong>Abandoned</strong> status.</td></tr><tr><td>5.</td><td>Text field "Change status to 'Abandoned' for tasks in 'In Progress' status after the specified number of minutes"</td><td>Allows specifying the number of minutes after which a Task in <strong>In Progress</strong> status will be changed to <strong>Abandoned</strong> status.</td></tr><tr><td>6.</td><td>Flag "Auto-change status of tasks in 'In Progress' to 'Failed (Application)' if the related Work has changed to 'Failed/Stopped/Interrupted'"</td><td>Allows enabling the auto-change function of the Task status from <strong>In Progress</strong> to <strong>Failed</strong> <strong>(Application)</strong> if the related Work has changed to <strong>Failed</strong>/<strong>Stopped</strong>/<strong>Interrupted</strong>.</td></tr><tr><td>7.</td><td>Flag "Auto-retry tasks in 'Failed (Application)' status"</td><td>Allows enabling the auto-retry function for Tasks in <strong>Failed (Application)</strong> status.</td></tr><tr><td>8.</td><td>Flag "Auto-retry tasks in 'Failed (Business)' status"</td><td>Allows enabling the auto-retry function for Tasks in <strong>Failed (Business)</strong> status.</td></tr><tr><td>9.</td><td>Flag "Auto-retry tasks in 'Abandoned' status"</td><td>Allows enabling the auto-retry function for Tasks in <strong>Abandoned</strong> status.</td></tr><tr><td>10.</td><td>Text field "Maximum number of retries"</td><td>Allows specifying the maximum number of retries for Tasks.</td></tr><tr><td>11.</td><td>Flag "Prohibit adding tasks with duplicate Names"</td><td>Allows enabling the function to prohibit adding Tasks with duplicate names to the Queue.</td></tr></tbody></table>

## **Editing a Previously Created Queue**

To view and edit the properties of a specific Queue, you need to select it from the list and click the icon ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-690447737878822a051c1768d4d44828fa21d624%2F2025-03-19_21-36-15.png?alt=media). After that, a form with the Queue settings will open, where you can make the necessary changes:

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

In addition to the fields filled in when creating the Queue, when editing, the form specifies the **GUID** (unique identifier assigned to the Queue after its creation) in the "Record GUID" field. This field cannot be edited.

## **Creating a New Task**

To create a new Task, you need to click the "Create" button in the "Tasks" table and fill out the opened form:

{% hint style="warning" %}
In order for the list of Tasks to appear in the "Tasks" table, you need to set the flag for one of the Queues.
{% endhint %}

The form contains the following elements:

<table data-header-hidden><thead><tr><th width="56"></th><th width="195"></th><th></th></tr></thead><tbody><tr><td><strong>#</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>Text field "Name"</td><td>Name of the Task. A required field.</td></tr><tr><td>2.</td><td>Text field "Description"</td><td>Description of the Task.</td></tr><tr><td>3.</td><td>Text field "Comment"</td><td>Comment for the Task.</td></tr><tr><td>4.</td><td>Field "Priority"</td><td><p>Priority of Task execution. Possible options:</p><ul><li>Low;</li><li>Normal;</li><li>High;</li><li>Deadline.</li></ul></td></tr><tr><td>5.</td><td>Text field "Tags"</td><td>Tags for the Task.</td></tr><tr><td>6.</td><td>Text field "Retries"</td><td>Number of retries for Task execution.</td></tr></tbody></table>

## **Editing a Previously Created Task**

To view and edit the properties of a specific Task, you need to select it from the list and click the icon ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-690447737878822a051c1768d4d44828fa21d624%2F2025-03-19_21-36-15.png?alt=media). After that, a form with the Task settings will open, where you can make the necessary changes:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-7c5f9d816fea2a507619d5a92eb0e346a59e5783%2F2025-04-19_21-32-53.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="55"></th><th width="208"></th><th width="483.7777099609375"></th></tr></thead><tbody><tr><td><strong>#</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>Text field "GUID"</td><td>Unique identifier assigned to the Task after its creation. This field cannot be edited.</td></tr><tr><td>2.</td><td>Text field "Status"</td><td><p>Status of the Task. Possible options:</p><ul><li>Created;</li><li>In Progress;</li><li>Successful;</li><li>Failed (Application);</li><li>Failed (Business);</li><li>Deferred until;</li><li>Abandoned.</li></ul></td></tr><tr><td>3.</td><td>Field "Deferred until"</td><td><p>Date and time until which the Task is deferred in the format: DD.MM.YYYY hours:minutes.<br></p><p>Upon reaching the "Deferred until" date and time, the Task is considered according to its priority and executed in the order of the Queue.</p></td></tr><tr><td>4.</td><td>Field "Deadline"</td><td>Date and time of the deadline for completing this Task.</td></tr><tr><td>5.</td><td>Field "Created"</td><td>Date and time when the Task was created. This field cannot be edited.</td></tr><tr><td>6.</td><td>Field "Updated"</td><td>Date and time when the Task was updated. This field cannot be edited.</td></tr></tbody></table>

## **Task Parameters**

For already created Tasks, "Task Parameters" are available. To open the parameters form, you need to click the icon . Three data types are available for specifying Task parameters:

* **Text**;
* **Table**;
* **Hash Table**.

The **Text** data type allows saving the necessary text as a Task parameter in the designated text field:

The **Table** data type allows creating and saving a table as a Task parameter in the designated table editor:

The **Hash Table** data type allows creating and saving a hash table (specifying key-value pairs) as a Task parameter in the designated fields, where the parameter is the key:

[Working with Tasks in Sherpa Designer is described here.](https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/rabota-v-sherpa-orchestrator/nachalo-raboty-v-sherpa-orchestrator/sozdanie-zadachi-v-orkestratore/rabota-s-zadachami-v-sherpa-designer)


---

# 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/sherpa-rpa/sherpa-orchestrator/rabota-v-sherpa-orchestrator/ekrany/ocheredi.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.