Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,7 @@
"build/agents/build-your-agent/tools",
"build/agents/build-your-agent/triggers",
"build/agents/build-your-agent/alerts",
"build/agents/build-your-agent/trigger-inventory",
"build/agents/build-your-agent/memory",
"build/agents/build-your-agent/variables",
"build/agents/build-your-agent/version-history",
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
---
title: 'Trigger status'
sidebarTitle: 'Trigger status'
description: 'View and manage triggers across all agents and workforces in your project from a single page.'
---

The trigger status page gives you a centralized view of every trigger in your project, whether it belongs to an agent or a workforce. Instead of opening each agent or workforce to check its triggers, you can see the full picture in one place and set up alarms on many triggers at once.

## Accessing the page

Click **Triggers** in the main sidebar. The page opens with the heading **Trigger status** and lists every trigger in your project.

<Note>
If you don't see **Triggers** in the sidebar, ask a project admin to check your permissions. In the classic sidebar, the entry only shows for users who can create agents and workforces.
</Note>

## Trigger table

The table has these columns:

- **Alarm**: a bell showing whether a failure alarm is set up for the trigger

Check warning on line 21 in site/content/docs/build/agents/build-your-agent/trigger-inventory.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

6 settings listed as bullet points — consider using a table instead so they're easier to scan. [technical: 6 consecutive bullet items matching **Key**: value or **Key** — value pattern]
- **Trigger**: the trigger's name, with an icon for its type
- **Belonging to**: the agent or workforce that owns the trigger. Click it to open that agent or workforce.
- **Status**: the trigger's current status
- **Last successful run**: when the trigger last ran successfully
- **Last failed**: when the trigger last failed

The table opens sorted by status, with failed triggers first. Click a column header to sort by that column (every column except **Alarm**). Use the search bar to filter by trigger, workforce or agent name.

### Grouping triggers

Use the tabs above the table to change how triggers are grouped:

- **All**: every trigger in one list
- **By workforce**: triggers grouped under the workforce that owns them
- **By agent**: triggers grouped under the agent that owns them

## Setting up an alarm on one trigger

Click the bell in a trigger's **Alarm** column:

- If the alarm is off, a modal opens where you choose the notification channels (email, Slack or Microsoft Teams). Save to turn the alarm on.
- If the alarm is on, clicking the bell turns it off straight away.

For details on notification channel setup, see [Alerts](/build/agents/build-your-agent/alerts).

## Bulk alarm actions

You can set up or mute alarms on many triggers at once.

### Selecting triggers

Each row has a checkbox in the leftmost column. Check one or more rows to select those triggers. Use the checkbox in the column header to select all triggers on the current page.

Your selection stays as you change pages, search or switch tabs, so you can build a selection across several pages before taking action.

When you select triggers, an action bar appears at the bottom of the page showing how many are selected (for example, "3 selected"). Click the count to see the selected triggers, and click the **x** next to one to remove it from the selection. Click the **x** at the right of the action bar to clear the selection.

### Setting up alarms in bulk

1. Select one or more triggers
2. In the action bar, click **Set up alarm**
3. In the modal that opens, choose the notification channels you want to use (email, Slack or Microsoft Teams)
4. Save to apply the alarm to all selected triggers

Triggers that already have an alarm get the channels you choose in place of their current ones.

While alarms are being set up, the action bar shows live progress (for example, "Enabling alarms… 3/10").

### Muting alarms in bulk

1. Select one or more triggers
2. In the action bar, click **Mute alarms**

Muting starts as soon as you click; there's no confirmation step. Only triggers whose alarm is currently on are muted, and the rest of the selection is skipped. If none of the selected triggers has an alarm on, the button is disabled.

### When some triggers fail

When a bulk action finishes, a message summarizes the result (for example, "Enabled for 7 triggers, 3 failed").

- **Triggers that can't be changed**, because you don't have permission or alarms aren't available for that trigger, are named in the message and removed from your selection.
- **Triggers that failed for other reasons** stay selected, so you can try again. When you click **Set up alarm** again, the modal is prefilled with the channels you just used.

Check warning on line 82 in site/content/docs/build/agents/build-your-agent/trigger-inventory.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

site/content/docs/build/agents/build-your-agent/trigger-inventory.mdx#L82

Did you really mean 'prefilled'?

Triggers that succeeded are removed from your selection.
1 change: 1 addition & 0 deletions site/content/docs/build/agents/meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
"build-your-agent/tools",
"build-your-agent/triggers",
"build-your-agent/alerts",
"build-your-agent/trigger-inventory",
"build-your-agent/memory",
"build-your-agent/variables",
"build-your-agent/version-history",
Expand Down
Loading