Machines

Group by Machine enabled

All the runtimes on one machine template are grouped together in one entry for each workstation that is connected to Orchestrator. The different blocks represent each such host machine. Hovering over each block displays an overview of that workstation:

Group by Machine disabled

The runtimes are displayed separately. The various statuses represent the health of each runtime. Each runtime is represented with a colored block. Hovering over each block displays an overview of that runtime:

Allows you to see the runtime allocation per host machine and machine template such that you can assess whether a machine needs more runtimes or not. Similarly, you can see if you have allocated too many runtimes to a machine.

Data in the table gets updated accordingly as you allocate more runtimes or start a job on a machine.

It illustrates the ratio between unresponsive, unlicensed, available and in use runtimes in a pie chart.

Displays the name of the executed process, if any, and details pertaining to the associated job. Specifically, the time at which the job execution began and its approximate time of completion. If there is no ongoing job, the widget is not populated. The estimated time of completion is calculated based on previous executions of that job, if any. If the job is at its first execution, a dash is displayed instead. When the execution has ended, the widget returns to the original, unpopulated state.

Filtering by Interval does not impact this widget.

Allows you to see a list of the errors encountered on the selected Robot. The errors are displayed in reverse chronological order as they occur, meaning a new error is always displayed at the top of the feed. The number of errors displayed in parentheses after the widget name is expressed according to your position within the feed and to the total number of errors. Let's say there are 453 errors in your feed. The following behavior is encountered:

After reaching the end of the feed, the total number of errors is displayed regardless of your position.

You can dismiss an error after having acknowledged it, however, please take into account that multiple users might check the feed simultaneously, so we recommend carefully using the Dismiss button. A dismissed error is still taken into account in the error counter. After an error was dismissed, the name of the user who performed the action is displayed adjacently in a tooltip. Note that you need Edit permissions on Monitoring to dismiss errors.

Allows you to see precise figures of the jobs finished on the selected Robot and their end state. It enables you to assess what is the success rate of the jobs executed on a Robot. Unfinished jobs are not taken into account.

Job states are represented with colors as follows:

The number in the middle of the chart represents the total number of jobs illustrated in the chart. The number on each slice represents the number of jobs in that specific state. You can filter out states by clicking the labels below the chart.

Precise figures of the queue items processed by the selected Robot and their final status. It provides metrics about the encountered exceptions enabling you to asses whether your queue items are failing or not.

Transaction states are represented with colors as follows:

The number in the middle of the chart represents the total number of transactions as illustrated by this widget. As an item gets successfully processed, the chart gets updated accordingly. The items are taken into account even if the impacted queue is deleted. You can filter out states by clicking the labels below the chart.