The Alerts page is a global page which displays notifications for Robots, queue items, triggers, jobs, processes, and tasks. The notifications appear in real time and can have Info, Success, Warn, Error or Fatal severity levels.
To open the Alerts page, click Alerts > See All Alerts.
When new alerts are generated, the Alerts icon is marked with a red notification badge. They are displayed as unread in the Alerts page. You can mark them as read individually or more at once by clicking Mark as Read.
Custom alerts can be sent to Orchestrator using the Raise Alert activity, which helps you add custom messages in the Alerts page, with a selected severity. The string added in the activity's Notification field is the message which appears in the Orchestrator Alerts page. All custom alerts are raised in Orchestrator under the Process component.
Alerts having either Fatal or Error severity are also included in emails if email configuration is done properly.
Please note that in order to execute this activity in Studio, the Robot has to be connected to Orchestrator and the Robot role needs to have View, Create, and Edit permissions on Alerts. The activity runs under the Robot which executes it.
You have the possibility to subscribe/unsubscribe from alerts on the Profile page for each of the following categories: Transactions, Robots, Jobs, Tasks, Triggers, and Queues.
The settings in this section are irrelevant if you don't have the corresponding View permissions on each alert category.
By default, in clean installations of Orchestrator, all the alert notifications are toggled on. If you upgraded your Orchestrator instance to 2019.10, only the Transactions, Robots, Jobs, and Triggers options are enabled, while the Queues and Tasks toggles are disabled.
Keep in mind that if you don't have the necessary permissions on one of the categories, the No Alerts icon is displayed next to it and you don't receive any of the corresponding alerts.
Let's say you want to subscribe only to transactions, jobs, and triggers. However, you do not have View permissions on Jobs. In this case, you receive alerts for transactions and triggers only, and the Alerts section looks as in the following screenshot:
Job not created
Robot is disconnected
Robot is unresponsive
Robot is available
BackgroundJob trigger misfired
BackgroundJob failed to execute
Queue item failed with ApplicationException
Queue item failed with BusinessException
User assigned as reviewer for failed/abandoned queue item
User assigned/unassigned/reassigned from one or multiple tasks
Trigger could not create a job as the maximum number of jobs has been reached. Occurs on queue triggers.
Trigger could not create jobs as the allocated Robots already have pending jobs for this process. Occurs on time triggers.
Process alert - alerts generated using the Raise Alert activity
Updated 2 months ago
|About Email Alerts|
|Setting Up Email Alerts|
|Alert Severity Levels|
|Field Descriptions for the Tenant Settings Page|