Robot queue
When you attempt to launch a robot (by any method), the system can send that launch to the robot queue.
Robot queue is a list of failed robot launches (failed to start or aborted due to an error) that the system will automatically try again in the order the launches appear in this list.
The number of launches is not equal to the number of robots. You can launch the same robot more than once and it will be different launches.
The reasons why a robot launch was sent to the robot queue are available in the section.
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.
The table displays:
- 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 |
|
"Added to queue" column | The date on which the robot was added to the queue |
"Launch condition" column | Specifies the robot's launch option Possible values:
|
"Initiator" column | A variant of the initiator record. Depends on how the robot is launched Possible values:
|
"Host" column | The name and IP address of the host on whose account the robot is running |
"Account" column | The account of the host on which the robot is running |
"Attempts" column | Number of attempts to launch the robot |
Button | 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 queue | Parameter names and designations | Where 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:
| 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:
Launch type | Reason for sending robot to queue |
---|---|
Manual launch of the robot "Robots" page |
|
Launch conditions based on resource queue |
|
Robot launch for the ROBIN Process workflow |
|
Robot terminated due to an error "Running robots" section | An error occurred while executing a running robot |
The runtime system installed on the selected host account failed to start launching (at this point, all of the above checks have already passed successfully and are not preventing launch) | An RDP session should be raised for the selected account, but the system failed to raise it. Accordingly, the launch cannot be started and is sent to the queue |
If the robot completed successfully or was stopped by the user, the system does not add such a launch to the queue.