Process Operation - Robot State and Operation¶
In the view Robot State and Operation, you can see at a glance the current status, the current deployment and the number of completed tasks of each Robot.
Privileges¶
In order to use Robot State and Operation, you require the Privilege Robot State and Operation Open.
Overview¶
In the Robot State and Operation view, every Customer Robot is displayed as an expandable box.
The sequence of the Robot boxes corresponds to the chronological sequence of the deployments. The Robot with the oldest deployment is displayed first, followed by the other Robots. This sequence is not changed.
The view is updated with a selectable rate.
Robot Box¶
The header of this box contains the name of the Robot, followed by its current status in parentheses.
Within this Robot box, every project that contains a configuration deployed for this Robot is displayed as a panel.
Project Panel¶
The header of the project panel contains the name of the project, followed by a colon and then the name of the configuration deployed for this Robot. This is followed by the status of the deployment and the time when this status was entered, both in parentheses. The header concludes with a dash and the current phase of the project.
States of a configuration¶
A configuration can have the states Running, Paused, or Suspended:
Every time the Robot is supposed to execute a Process, based on the schedule, it checks all the conditions listed below and sets the status accordingly.
If a configuration is revoked from a Robot, it is no longer listed in the Robot State and Operations view.
Running¶
As soon as the configuration is deployed to a Robot and the configuration is within the service time of the Robot and outside the downtime of the Process Applications used, it enters the state Running.
Suspended¶
If the Robot does not have a service time or a process application has a downtime, the configuration enters the state Suspended.
Paused¶
If the configuration is paused manually by a user in the Manage configurations and deployments view, it enters the state Paused.
This status is set and ended manually.
Data of a configuration¶
The data relevant to a Robot is listed in a table for each configuration:
Secure session¶
The Secure Session column shows all the secure sessions that the Robot can use for this configuration in a numbered list.
A 1 also appears here if the Robot is configured for desktop sessions.
State¶
The State column contains the state of process processing by the Robot.
The following graphic shows a highly simplified representation of the process workflow:
Free¶
If processing is in the state Free, it is outside the schedule or between two process runs. This can be the case, for example, if the Process should only be executed once per week. The Robot checks the time interval defined in the X1 Bot Configurator, under Common: Check, to see whether the runtime of a schedule has begun, whether it is within a service time, and whether the required applications are outside their downtimes. If everything is okay, processing enters the state Searching; otherwise it remains in the state Free.
Searching¶
As soon as the Process is to be started according to the schedule, and the Robot is within the service time and all required applications are outside their downtime, the Robot starts to execute the trigger workflow. In the trigger workflow, the conditions that have to be met for the Process to be executed are checked. In other words, the Robot searches for work. Processing enters the state Searching. If the search is not successful, processing returns to the state Free; if there is something to do, it enters the state Waiting.
Waiting¶
If the Process is to be executed, the Robot waits for the next activity workflow to execute. Processing enters the state Waiting. If an activity workflow is to be executed, processing enters the state Processing; otherwise it returns to the state Free.
Processing¶
When the Robot executes an activity workflow, processing has the state Processing. After each execution of an activity workflow, processing initially returns to the state Waiting. The Robot waits to see whether another activity workflow has to be executed. If an activity workflow is to be executed, processing enters the state Processing; otherwise it returns to the state Free.
Since¶
Time when processing last entered the state listed under State.
Process instance¶
ID of the process instance currently being executed. The ID is displayed in the states Waiting and Processing. As soon as the Robot finds work in the trigger workflow, a new ID is generated.
Activity¶
In the Processing state, the Activity column displays the name of the activity workflow that is currently being executed.
Work done¶
Number of process runs executed successfully since the time noted under Running since in the header.
The number of executed trigger workflows can be greater than the number specified under Work done.
Menu¶
Refresh¶
Select the refresh rate from the drop-down menu and click on the button Apply to implement your selection.
Collapse / Expand¶
Clicking the Collapse icon reduces the Robot box to Robot name and state. Clicking the Expand icon expands the Robot box to the view described above.