Robot execution

Use this tab to define properties for RoboServer robot execution. Specify how many robots can run concurrently and how many can be queued on each RoboServer.

If you are using a CRE license, the maximum number of robots that can run concurrently in clusters is defined by the license.

Property	Description
Max concurrent robots	Maximum number of robots allowed to execute concurrently on each RoboServer. Lower the max number if your robots are CPU and/or memory intensive and running them often reaches the memory threshold. Default is 5.
Max queued robots	Maximum number of robots allowed to reside in the queue of each RoboServer. If robots are started via API calls, the value determines how many robots can be queued on each RoboServer. Use this setting only with deprecated methods such as SocketBasedObjectRQLProtocol in the Java API to call RoboServers directly without calling the cluster. Using deprecated methods is not recommended. Default is 10.

Property

Description

Max concurrent robots

Maximum number of robots allowed to execute concurrently on each RoboServer.

Lower the max number if your robots are CPU and/or memory intensive and running them often reaches the memory threshold.

Default is 5.

Max queued robots

Maximum number of robots allowed to reside in the queue of each RoboServer.

If robots are started via API calls, the value determines how many robots can be queued on each RoboServer.

Use this setting only with deprecated methods such as SocketBasedObjectRQLProtocol in the Java API to call RoboServers directly without calling the cluster. Using deprecated methods is not recommended.

Default is 10.