UiPath Orchestrator

The UiPath Orchestrator Guide

The Alerts page is a global page which displays notifications for robots, queue items, triggers, jobs, processes, and tasks. Alerts are sent in real time and can have one of the following severity levels: Info, Success, Warn, Error or Fatal, and can fit in one of the following components: Robots, Transactions, Triggers, Jobs, Process, Tasks, Queues.

To navigate to the Alerts page, click the Alerts icon and then See All Alerts in the notification panel.


When new alerts are generated, a red notification badge appears on the Alerts icon. New alerts are displayed as unread in the Alerts page.
To dismiss an alert, click the Mark as Read button corresponding to it.
To dismiss multiple alerts at once, select them and click the global Mark as Read button at the top of the page.

Alert Notification Panel

The notification panel displays a maximum of 5 alerts ordered according to severity and creation time. Higher severity alerts are displayed first; if there are several alerts with the same severity, they are displayed in reverse chronological order. Dismissing an alert on the Alerts page removes it from the notification panel.


From the notification panel you can navigate to the Alerts page by clicking See All Alerts, or to the Profile page by clicking Open Alerts Preferences.

Custom Alerts

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.


Subscribing/Unsubscribing from Alerts



The settings in this section are irrelevant if you don't have the corresponding View permissions on each alert category.

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.

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 no_alerts 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:


Alert Classification

JobsErrorJob faulted
JobsErrorJob not created
RobotsFatalRobot is disconnected
RobotsErrorRobot is unresponsive
RobotsInfoRobot is available
SchedulesErrorBackgroundJob trigger misfired
SchedulesErrorBackgroundJob failed to execute
TransactionsErrorQueue item failed with ApplicationException
TransactionsWarnQueue item failed with BusinessException
TransactionsInfoUser assigned as reviewer for failed/abandoned queue item
QueuesErrorA breach of the SLA is predicted for a queue.
TasksInfoUser assigned/unassigned/reassigned from one or multiple tasks
TriggersErrorTrigger could not create a job as the maximum number of jobs has been reached. Occurs on queue triggers.
TriggersErrorTrigger could not create jobs as the allocated Robots already have pending jobs for this process. Occurs on time triggers.
ProcessSuccessProcess alert - alerts generated using the Raise Alert activity

Updated 6 days ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.