---
title: Alerts
slug: alerts
docTags: 
createdAt: 2025-10-21T04:57:21.000Z
---

The **Alerts **section in Swimlane Turbine provides visibility into alert notifications generated when playbook runs fail. It complements the configuration of orchestration alerts by showing administrators the history of triggered alerts within a selected timeframe.

## Overview

The Alerts page displays a table of alerts, including:

- **Alert** – The type of alert generated.
- **Time of Alert** – When the alert was triggered.
- **Details** – Additional information about the failure or notification.

If no alerts are available for the selected time range, the table will display an empty state message: *“No alerts available for the selected time range.”*

## Time Range Filtering

You can filter alerts by selecting a time window (for example, Last 24 Hours, Last 7 Days, or Last 30 Days). This allows administrators to focus on recent issues or review longer-term trends in orchestration failures.

## Configuring Orchestration Alerts

To enable and configure alerts:

1. In the **Admin Panel**, navigate to **Settings > Tenant-specific > Orchestration Alerts**. 
2. Enable the **Send via Email** option by selecting the checkbox. 
3. Once enabled, a **Recipients** field will appear. Here you can specify: 
   - **Users** – Directly assign alerts to specific Swimlane users. 
   - **Groups** – Assign alerts to Swimlane groups to ensure multiple team members are informed. 
   - **Custom Email IDs** – Add external addresses if notifications need to go to recipients outside of Swimlane. 

Administrators can add recipients by searching for Swimlane users or groups, or by typing a new email address. Deactivated users or groups will not receive notifications.

When a playbook run fails, Swimlane generates an **email notification** that contains a direct link to the failed playbook. This allows administrators to quickly open the failed run and begin troubleshooting.

## Alert Behavior

- **Immediate Notifications** – A failure triggers an alert email right away. 
- **Summary Notifications** – If another failure occurs within 30 minutes, instead of sending multiple emails, Swimlane sends a single summary email. This email contains a list of all failed playbook runs within that period, along with their corresponding Playbook IDs. 

This approach ensures administrators stay informed without being overwhelmed by excessive notifications.

## Example Email Notification

A typical orchestration alert email includes:

- The **Playbook Name and ID** 
- The **time of failure** 
- A **direct link** to the failed run in Swimlane Turbine 

Clicking the link takes you directly to the corresponding playbook run, saving time in locating and diagnosing the issue.

## Benefits of Orchestration Alerts

- **Immediate Awareness** – Administrators are informed as soon as failures occur. 
- **Actionable Links** – Direct navigation to failed playbook runs speeds up investigation. 
- **Reduced Noise** – Summary notifications prevent inbox flooding from repeated failures. 
- **Tenant-Specific Configuration** – Alerts can be tailored for each tenant’s needs, ensuring relevance. 

By enabling orchestration alerts, organizations can ensure quick response to failures, reduce downtime, and maintain high reliability of their automated workflows.