- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Audit
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
Notifications
You can receive notifications for a variety of events related to your Orchestrator activity, as well as for the folders you choose.
Notifications are managed from the Notifications section of your user preferences, which you can access in two ways:
- By clicking the icon with your initials, in the top right-hand corner of the navigation bar.
- By clicking the cog icon in the Notifications panel.
Once you subscribe to be alerted for the events or severity levels of your choice, notifications are displayed in the Notifications panel, which you can access by clicking the bell icon in the top right-hand corner of the navigation bar.
You can read more about this framework in My notifications and Managing notifications.
To view notifications, you need the following permissions:
- View on Alerts at the tenant level
- View on the specific component in the folder for which you want to receive notifications
If an alert requires two permissions, those permissions must be granted via direct user-level assignment or via the same group. If they are granted via two separate groups, the alert is not sent.
- For alerts covering
tenant-scoped actions, grant the following permissions to the same group:
- View on Alerts at the tenant level
- View on the specific tenant-scoped component at the tenant level
Example: The "Machine disconnected" alert requires View on Alerts and View on Machines at the tenant level, within the same group.
- For alerts covering
folder-scoped actions, grant the following permissions to the same group:
- View on Alerts at the tenant level
- View on the specific folder-scoped component at the folder level
Example: The "Job faulted" alert requires View on Alerts at the tenant level and View on Jobs at the folder level, within the same group.
This table lists the events that you can subscribe to, their corresponding severity level, and the permission required to receive each notification.
Event category |
Event |
Severity |
Required permissions |
---|---|---|---|
Robots |
Unattended robot is available |
Info |
|
Unattended robot is unresponsive |
Error |
| |
Unattended robot is disconnected |
Fatal |
| |
Attended robot is unresponsive |
Info |
| |
Attended robot is disconnected |
Info |
| |
Triggers |
Trigger misfired |
Error |
View on Triggers |
Trigger automatically disabled |
Fatal | ||
Trigger automatically disabled after job failures |
Fatal | ||
Trigger failed to create jobs |
Error | ||
Jobs number limit reached for process |
Info | ||
Connected Triggers |
No connection found in order to create event trigger |
Error |
View on Connections |
Event trigger creation failed |
Error | ||
Connected event trigger deletion failed |
Error | ||
Jobs |
Job execution failed |
Error |
View on Jobs |
Jobs execution in pending |
Error | ||
Job execution running timeout |
Error | ||
Process retention error |
Error | ||
Queue Items |
Transaction failed with application exception |
Error |
View on Transactions |
Transaction failed with business exception |
Warn | ||
Reviewer assigned |
Info | ||
Queues |
Queue SLA error |
Error |
View on Queues |
Queue retention error |
Error | ||
Process |
Process notification |
Info |
View on Processes |
Process notification |
Warn | ||
Process notification |
Error | ||
Process notification |
Fatal | ||
Process notification |
Success | ||
Folders |
Folder delete succeeded |
Success |
View on Folders |
Folder delete failed |
Error | ||
Folder migration succeeded |
Success | ||
Folder migration failed |
Error | ||
Personal Workspaces |
Personal workspaces enabled |
Success |
N/A |
Enabling personal workspaces failed |
Error | ||
Finished exploring personal workspaces |
Success | ||
Personal workspaces exploration failed |
Error | ||
User started exploring your personal workspace |
Error | ||
User finished exploring your personal workspace |
Info | ||
Finished exploring your personal workspace |
Info | ||
Personal workspace converted to folder |
Info | ||
Personal workspace deleted |
Info | ||
Export |
Export completed successfully |
Success |
N/A |
Export failed |
Error | ||
Test Automation |
Automation test operation finished |
Info |
N/A |
Serverless |
Problem synchronizing VPN settings to Serverless Control Plane |
Warn |
View on Machines |
Failed to synchronize VPN settings with Secure Control Plane |
Error | ||
Problem with machine and secrets synchronization |
Warn | ||
Machine and secrets synchronization failed |
Error | ||
Problem with machine synchronization to Serverless Control Plane |
Warn | ||
Machine synchronization to Serverless Control Plane failed |
Error | ||
Serverless VPN success events |
Success | ||
Serverless VPN warning events |
Warn | ||
Serverless VPN error events |
Error | ||
Serverless VPN fatal events |
Error | ||
Cloud Robots |
Cloud Robots pool events |
Warn |
View on Machines |
Cloud Robots virtual machine error events |
Error | ||
Cloud Robots virtual machine information events |
Info | ||
Cloud Robots images error events |
Error | ||
Cloud Robots images information events |
Info |