The Alerts page displays notifications for Robots, queue items, schedules, and jobs. The notifications appear in real time and can have Info, Success, Warn, Error or Fatal severity levels.
A user with no assigned Organization Unit does not have access to Alerts, even if organization units are enabled.
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, and Schedules.
The settings in this section are irrelevant if you don't have the corresponding View permissions.
By default, all 4 toggles are enabled for a host admin.
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 unsubscribe from transaction-related alerts, subscribe to jobs and schedules-related ones and, at the same time, you don't have View permissions on Robots. In this case the Alerts section should look 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
Process alert (alerts generated using the Raise Alert activity in Studio)
* “Robot is unresponsive” alerts are received despite having Robot alerts disabled.
|About Email Alerts|
|Setting Up Email Alerts|
|Alert Severity Levels|
|Field Descriptions for the Tenant Settings Page|