Сравнение версий

Старая версия 7

changes.mady.by.user Рукобратская Анна

Сохранено

по сравнению с

Новая версия Текущий

changes.mady.by.user Рукобратская Анна

Сохранено

Ключ

  • Эта строка добавлена.
  • Эта строка удалена.
  • Изменено форматирование.

Оглавление
maxLevel2

Robot queue

When you attempt to launch a robot (by any method), the system can send that launch to the robot queue.   

...

The interface of the Robot queue section is available in the Orchestrator section:

Robot queue table description

The table contains a list of robots that are not currently running.

...

  • Name and version of the robot, and the need for a graphics session for operation
  • Time when an unlaunched robot was added to the robot queue
  • Method of launching the robot
  • Initiator of the launch
  • Host on whose account the robot is launched
  • Account on which the robot is started
  • Number of attempts to launch the robot

Table columns and buttons description

Column/button name

Description

"Robot" column
  • Robot name
  • Robot version
  • Indicator that shows whether the host account needs a GUI for the robot to work. If  is displayed , it means that the GUI is required, if  - it is not required
"Added to queue" columnThe date on which the robot was added to the queue
"Launch condition" column

Specifies the robot's launch option

Информация

Possible values:

  • "Manual launch" - the robot was launched by the user. The column next to the phrase also displays the name of the application through which the robot was launched: "Robin Studio", "Robin Player" or "Orchestrator"
  • "Launch condition (Resource queue)" - the robot was started by a condition based on the resource queue.
  • "Launch Condition (Schedule)" - the robot was started by a condition based on a schedule (configured via Orchestrator, not Player).
  • "Process" - the robot was launched as part of a digital employee's workflow execution.
  • "Robot" - the robot was started by another robot.


"Initiator" column

A variant of the initiator record. Depends on how the robot is launched

Информация

Possible values:

  • "Manual launch" - the name of the user who launched the robot is displayed
  • "Launch condition (Schedule)" - displays the name of the launch condition. This name is a link (button), which can be used to go to the card of this launch condition (opened in read mode). If you click on the "Return" button in the card, the "Launch history" tab in the account card returns. If the launch condition is not found in the current tenant or is unavailable to the user, its name remains as a link, but nothing opens when clicked, a warning appears:
    "Error while working with launch condition. No launch condition found"
  • "Launch condition (Resource queue)" - displays the name of the launch condition. This name is a link (button) to the card of this launch condition (opens in read mode). The name of the condition is a link to its card, which is opened in the "read only" mode. If you click on the "Return" button in the card, the "Launch history" tab in the account card returns. If the launch condition is not found in the current tenant or is unavailable to the user, its name remains as a link, but nothing opens when clicked, a warning appears:
    "Error while working with launch condition. No launch condition found"
  • "Process" - the name of the workflow within which the robot was launched is displayed
  • "Robot" - displays the name and version of the robot that launched the robot in question. Also displayed is an indicator that indicates whether the host account needs a GUI for the robot to work. If is displayed , it means that the GUI is required, if - it is not required


"Host" columnThe name and IP address of the host on whose account the robot is running
"Account" columnThe account of the host on which the robot is running

"Attempts" column

Number of attempts to launch the robot

Button image-2024-5-29_12-44-37.png

By clicking on it, the records in the table are updated

Parameters affecting the operation of the robot queue

Parameters affecting the operation of the robot queueParameter names and designationsWhere installed
Robot queue parameters
 

Current number of restart attempts made = r

Waiting time between restarts = t

Both parameters are configured in the system configuration file

Limit of launches in progress

Set in the system configuration file when the system is deployed. The parameter is common for all hosts, i.e. you cannot set different limits for different hosts. In this case, workflows (robot projects) launched via ROBIN Studio are not counted in the total number of current launches

Maximum number of restarts. Some launches may be queued indefinitely, for example if there is a problem with the robot itself and it needs to be modified via ROBIN Studio. To prevent the queue from becoming clogged with such launches, once a launch has been queued, the system will attempt to re-run it only a set number of times

When the number of attempts is equal to the number set in the configuration file, the system deletes the launch from the queue and does not monitor it any further

Set in the configuration file

Timeout. This is the amount of time that must elapse from the time a launch is queued (the first time or on a failed restart attempt) before the system will attempt to execute that launch again

Подсказка

Example of how this parameter works:

  1. The robot fell into an error and the system sends this launch to the queue
  2. An event occurs in which the system repeats launches in the queue
  3. Since the launch was sent to the queue, the time equal to the value in the configuration file has not yet elapsed. Therefore, the system skips this launch and leaves it in the queue.
  4. The number of restarts performed for this launch remains unchanged
  5. After some time, the event triggering the queue check occurs again
  6. The time equal to the value from the configuration file has already passed since the launch was added to the queue. This time the system does not miss this launch and tries to start its execution
  7. Regardless of the result (whether the launch succeeded or failed), the number of restarts for this launch is increased by 1


Set in the configuration file
Parameters of launch conditions based on resource queue

Number of resources for the first launch = N

Number of robot instances = D

Number of resources for additional launches = M

Number of robot instances to be executed at this moment given the current number of queue resources = L

Current number of robot instances to be executed = n

All parameters except L and n are configured in the launch condition card

Adding a launch to the queue

Events in which the system attempts to retry launches that have been queued:

  • A robot in progress has finished its work, i.e. one of the host accounts has made room for another launch
  • Credentials have been added or updated to the host account card
  • One of the host accounts has become active, and the number of launches running on it is not greater than the set launch limit

Reasons why a robot launch will be sent to the queue

The robot launch will be sent to the queue if it fails to launch, depending on the launch conditions:

...