Skip to main content
Kofax

Robot Queuing

Article # 3036545 - Page views: 251

Issue

How are robots queued when the RoboServer can't run them?

Solution

In the Cluster Settings > Robot Execution administrators can define a value for "Max Concurrent Robots" (default value is 20). This defines how many robots could run at the same time on a RoboServer (that is part of this cluster).

Tip-Icon.png

Keep in mind that in the CRE licensing model, the number of assigned CRE per RoboServer also limits the concurrent robots.

E.g. If  "Max Concurrent Robots" is set to 20, but the RoboServer has 5 CRE assigned, then only 5 robots will be able to run concurrently on the RoboServer, regardless of the "Max Concurrent Robots" value.


When a robot is started, one of the first things that are checked is if the cluster on which the robot should run has free "slots" for this robot (i.e. the cluster has at least one RoboServer that is running a number of robots less than "Max Concurrent Robots").

If there are no RoboServers with available slots, the robot could be queued or return a message. The behavior depends on how the robot is started.

 

Kofax RPA uses two different queues for robots, if needed:

1. Management Console queue. This queue doesn't have a set maximum size.

2. RoboServer queue. The size of this queue can be configured in Management Console > Admin > RoboServers > Cluster Settings > Robot Execution > Max Queued robots

Here is the intended behavior when there aren't available slots for a robot, depending on how the robot was started:

How the robot was started Result (when no slots available)
  • Kapplets from v10 and Earlier

The robot is queued on the Management Console queue.

The list of running and queued robots can be seen in Management Console > Task View

  • Schedule

The robot is queued on the Management Console queue.

The list of running and queued robots can be seen in Management Console > Task View

in v11.1 and later the schedules have a timeout in their settings (how long to be queued) - 10 minutes, by default.

The list of the tasks (robots) that are queued, running, completed or timed out can be seen in the Task Messages log.

  • .net /Java API (legacy)

The robot is queued on the RoboServer Queue.

If "Max Queued robots" is 0, the robot will return an error about not being able to run (e.g. "No slots available")

  • New Kapplets from v11.0 and v11.1

These runs don't get queued. If there are no available RoboServers or no available slots on the RoboServers, the run fails (there is an error message in the Kapplets log files)

  • New Kapplets v11.2 and Later *

The robot is queued on the Management Console queue.

Check the Task Messages log to see the list of queued/ running/ completed or timed out tasks.

  • manually (from Repository)
  • REST request
  • SOAP request

These runs don't get queued. This is because running the robots in this way is supposed to be a short lived request so they don't get put in any queue.

If the cluster on which these robots should run doesn't have any slots available, the output of the robot will contain a message about this ("No slots available").

  • using the Management Console REST API to queue Tasks (from v11.1 and later)

The robots (tasks) are queued on the Management Console for an amount of time and with a priority specified in the REST call.

Check the Task Messages log to see the list of queued/ running/ completed or timed out tasks.

 

Level of Complexity 

Moderate

 

Applies to  

Product Version Build Environment Hardware
Kofax RPA ALL      

References

Add any references to other internal or external articles

 

  • Was this article helpful?