Queues

Allows you to see an overview of the queue's health state so you can assess if there are any problems that would impact the entire system. Each color block represents a specific queue from your instance. Hovering over a block displays the name of the corresponding queue and its containing folder. Note that it is possible to have multiple queues with the same name if each is in a different folder. The total number of queues is displayed in parentheses after the widget name. As a queue's state changes, the chart gets updated and the block color changes accordingly.

The various scenarios are represented with colored blocks and tooltips as follows:

Clicking a block displays the corresponding detailed view page. Click the arrow at the top-left of the page to return to the general view.

Filtering by Interval does not impact the red blocks in this widget.

Allows you to see the overall status of all queue items so as to assess if your system is overloaded, and more Robots are needed to process everything in time. Starting an item-processing job causes the Items in Progress section to update accordingly.

The unprocessed queue items are broken down into three categories:

Filtering by Interval only impacts the Newly Added Items section in this widget.

Allows you to see precise figures on items that were processed. It enables you to assess whether your queue items are failing or not. Please note that for failed items that were retried, each retry status is taken into account.

Transactions 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. The number on each slice represents the transactions in that specific state. Once an item is processed, successfully or not, the chart gets updated accordingly.

Allows you to see the timeline of processed items broken down according to their final status, in the selected interval. Please note that for failed items that were retried, each retry status is taken into account.

Transaction states are represented with colors as follows:

Once an item-processing job has finished or it has been stopped, the chart gets updated accordingly. Click a marker in the chart to see the exact corresponding value.

Allows you to see information pertaining to each queue and the corresponding items metrics. The total number of queues is displayed in parentheses after the widget name.

Filtering by Interval does not impact this widget.

Allows you to see precise figures on items that were processed in the selected queue. It provides metrics about the encountered exceptions so that you can asses whether your queue items are failing or not. Please note that for failed items that were retried, each retry status is taken into account.

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. Once an item is processed, successfully or not, the chart gets updated accordingly. You can filter out states by clicking the labels below the chart.

Allows you to see unprocessed items in a queue broken down into two categories:

This enables you to see the overall status of all the items in a queue so as to assess if your system is overloaded, and more Robots are needed to process everything in time. Starting an item-processing job causes the Items in Progress section to update accordingly. You can filter out states by clicking the labels below the chart.

Allows you to see the number of items in the selected queue that were either added or processed, in the selected interval, thus enabling you to assess the efficiency of your system concerning item processing. You can filter out states by clicking the labels below the chart.

Enables you to see your successfully processed queue items broken down according to the number of retries. The number of retries for successfully executed items are also taken into account in this widget. You can filter out states by clicking the labels below the chart.

Allows you to see the timeline of processed items in the selected queue, broken down according to their final status, in the selected interval. Please note that for failed items that were retried, each retry status is taken into account.

Transaction states are represented with colors as follows:

Once an item-processing job has finished or has been stopped, the chart gets updated accordingly. Click a marker in the chart to see the exact corresponding value.

Enables you to see the average handling time of an item, calculated on all items in the selected queue since it was created, and the estimated completion time for the rest of the items based on that average. The Estimated Completion value is influenced by the number of Robots which are currently processing items, as well as by items that have a Defer Date. When no more unprocessed items are left in the queue, the value is set to N/A.

Filtering by Interval does not impact this widget.

Note that the durations are displayed as rounded-up values. The exact duration in ISO8601 format is shown when you hover over the displayed value.

Allows you to see the a list of the errors encountered on the selected queue. 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.