Welcome to Kofax RPA > Management Console > Management Console Configuration and User Interface > Admin > RoboServers > Change the Cluster State

Change the Cluster State

You can set two different states to a cluster: Running or Paused. The Paused state sets clusters to a state where nothing is run on them. This helps updating cluster settings in a way that ensures that all robots in a given schedule use the same settings, and that settings are not changed in the middle of schedule runs. The table below explains the different states.

Cluster State

Description

Running

Cluster operates normally with schedules and individual robots executed as expected. Cluster settings are not "applied" to the RoboServers so that settings are not changed in the middle of schedule runs.

Paused

Cluster is not allowed to accept new execution requests and the RoboServers finish all current executions. Cluster settings can be changed. For example, a database mapping can be changed.

  1. Click Change Cluster State above the cluster list.

    The Change Cluster State window appears.

    Note You can also right-click a cluster in the list and select the appropriate submenu item.
  2. In the Cluster field, select the cluster to change.
  3. In the Cluster State field, select a Paused option to transition into Paused state.

    The cluster states are, as the name implies, only relevant on a cluster level. As such, they are a way for the Management Console to control when tasks can be executed on clusters. They do not, however, control the individual RoboServers. This means that robots started from the API are not stopped when going into Paused state. Therefore, the settings of a RoboServer can be updated while API robots are running. It is guaranteed, though, that robot settings are not updated during its execution. For instance, if databases are updated while one or more API robots are running, the robots will use the databases that were configured when they started. Next time they are run, they will use the new settings.