> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage and monitor automations

> Find CodeRabbit automations in the web app, follow their runs, run them on demand, pause, resume, or delete them, and control who can manage them and how much they spend.

Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.)

The **Automations** section of the CodeRabbit web app lists every automation in the workspace, wherever it was created, and shows each run.

## The Automations page

Select **Automations** > **Home** in the sidebar. The page starts with **Templates** for new automations, followed by the list of automations, split into **My automations** and **Other workspace automations**.

| Column | Shows |
| - | - |
| **Name** | The automation's name |
| **Trigger type** | Scheduled, channel message, or webhook |
| **Destination** | Where results go |
| **Created by** | The automation's creator |
| **Automation spend** | What the automation has spent, when you can see spend |
| **Status** | Active or paused |
| **Actions** | **Edit**, **Pause automation** or **Resume automation**, and **Delete automation** |

Use **Search automations...** to find an automation by name, and the **All trigger types** and **All statuses** filters to narrow the list. Select an automation to open its details.

The **Automations Agent usage** notice at the top of the list shows trial and billing status. See [Who can use Automations](https://docs.coderabbit.ai/automations.md#who-can-use-automations).

**Slack** > **Automations** and **Discord** > **Automations** show the automations for that platform, along with their **Prebuilt automations**.

## Automation details

![The page of an example scheduled automation named Release blockers digest, marked Active. Run now and Edit buttons are at the top right. Stat tiles show 10 total runs, a 100% success rate, an average duration of 318.8 seconds, and a last trigger 5 hours ago. The Overview tab shows the trigger, every week on Monday and Thursday at 10:00, and Actions, delivers to 1 destination. Active runs is empty, and Recent runs lists three successful runs that posted the digest.](https://mintcdn.com/coderabbit/gKPHgRl-bneGQ2yQ/assets/images/automations-detail.webp?fit=max\&auto=format\&n=gKPHgRl-bneGQ2yQ\&q=85\&s=84fdcb45a56f0d21bceb31dcfa553bc2)

An automation's page, with example data: totals, the trigger and its delivery, and recent runs

The automation's page shows its status and these controls:

* **Run now**: starts a run of an active scheduled automation. See [Run now, pause, resume, and delete](#run-now-pause-resume-and-delete).
* **Edit**: opens the automation editor. See [Edit an automation](https://docs.coderabbit.ai/automations/create.md#edit-an-automation).
* The overflow menu: **Pause automation** or **Resume automation**, and **Delete automation**.

The page has two tabs.

### Overview

* **Total runs**, **Success rate**, **Avg. duration**, and **Last triggered**.
* A summary of the trigger and destinations. Select **Show trigger details** or **Show delivery destinations** for the full configuration.
* **Active runs**: runs that are scheduled or running. A running run shows its latest step; select **Show activity** to see everything it has done so far.
* **Recent runs**: the latest five runs. Select **View all** to open **Run history**.

### Run history

**Previous runs** lists every finished run, 10 per page, with its **When** and **Duration**. Select **Open run** to see what the run did.

A run has one of these statuses:

| Status | Meaning |
| - | - |
| Scheduled | The run is queued to start. |
| Running | The run is in progress. |
| Succeeded | The run finished and delivered its result. |
| Failed | The run stopped with an error, or couldn't start, for example because billing access was unavailable. |
| Skipped | The trigger fired, but the run didn't start, for example because the automation wasn't active or another operation on it was in progress. |

Webhook deliveries that match no rule, and repeated deliveries removed by [deduplication](https://docs.coderabbit.ai/automations/triggers.md#deduplication), don't create runs and don't appear here.

If you can view an automation but not manage it, its page is read-only and doesn't show the last run's summary.

## Activity

**Automations** > **Activity** lists runs across all the automations you can see. Use it to compare runs and track Agent minutes.

| Filter | What it narrows |
| - | - |
| Search | Runs by text |
| **Automation** | Runs of one automation |
| **Date range** | Runs between **From** and **To** |
| **Agent minutes** | Runs between **Min minutes** and **Max minutes** |

Each row shows when the run happened, its Agent minutes ("Not recorded" when unknown), and who or what triggered it. Select a run to open its details. The list refreshes every 30 seconds; select **Refresh** to update it right away.

**Slack** > **Activity** and **Discord** > **Activity** also include conversations with CodeRabbit Agent and filter by scope, channel, and user. See [Usage in Slack](https://docs.coderabbit.ai/slack-agent/usage.md).

## Run now, pause, resume, and delete

| Action | Where | Effect |
| - | - | - |
| **Run now** | The automation's page | Starts a run immediately and returns you to **Overview** to follow it. Available only for active scheduled automations. |
| **Pause automation** | The automation's page or the list | Stops new runs. The configuration is kept. |
| **Resume automation** | The automation's page or the list | Turns the automation back on. CodeRabbit checks billing before it resumes. |
| **Delete automation** | The automation's page or the list | Deletes the automation after you confirm. The automation and its run history disappear from the Automations page, **Activity**, and the CodeRabbit API, and you can't restore them. |

Channel message and webhook automations can't be run on demand. To test them, see [Test a trigger](https://docs.coderabbit.ai/automations/triggers.md#test-a-trigger).

The web app has no control to stop a run in progress. Slack and Discord automations can be stopped from their channel. See [Manage automations in Slack](https://docs.coderabbit.ai/slack-agent/automations.md#manage-automations-in-slack).

The CodeRabbit API supports the same actions with `run_now`, `pause`, `resume`, and `delete` commands. See [Create automations with the API](https://docs.coderabbit.ai/automations/create.md#create-automations-with-the-api).

## Permissions

CodeRabbit admins, members with the **Admin** [role](https://docs.coderabbit.ai/management/roles.md), can see and manage every automation. Everyone else can see and manage the automations they created, and can see some others read-only:

| Automation | Who can see it |
| - | - |
| Created in the web app without a Slack or Discord destination | All workspace members |
| In a public Slack or Discord channel | All workspace members |
| In a private channel or a DM | The creator and CodeRabbit admins |

The **Automation admin** role adds to member access: managing other people's automations that were created on the Automations page without a Slack or Discord destination, and automations in public channels. The first two rows describe the web app; the last two describe Slack and Discord:

| Action | Creator | CodeRabbit admin | Automation admin | Other members |
| - | - | - | - | - |
| Edit, pause, resume, or delete in the web app | Yes | Yes | Automations created in the web app and public-channel automations, never private-channel or DM automations | No |
| **Run now** in the web app | Yes | Yes | Where they can manage the automation | No |
| Run now or stop in a Slack or Discord channel | Yes | Yes | Yes | Yes, if they're in the channel |
| Run now or stop in a DM | Yes | Yes, as can a Slack workspace admin | No | No |

To assign the role, see [Automation admins](https://docs.coderabbit.ai/slack-agent/admin-and-security.md#automation-admins). For who can create automations, see [Who can create automations](https://docs.coderabbit.ai/automations/create.md#who-can-create-automations).

## Archived automations

CodeRabbit archives an automation automatically when its place to run or deliver is gone. Archiving is different from pausing: you pause an automation yourself, and CodeRabbit archives it. An automation is archived when:

* It was a one-time automation and has run.
* Its creator left the workspace.
* The CodeRabbit app was uninstalled from the Slack workspace or Discord server.
* Its channel was deleted, or CodeRabbit lost access to it.
* Its DM can't be used anymore.
* It replies in a fixed thread, and the thread's first message is gone.

For details on Slack, see [Archival](https://docs.coderabbit.ai/slack-agent/automations.md#archival).

## Spend limits

Automation runs use Agent minutes. Three limits can cap their spend:

| Limit | Where | Applies to |
| - | - | - |
| Monthly Agent spend cap | Billing | All Agent usage in the organization, including automations without a Slack or Discord destination. See [Monthly spend cap](https://docs.coderabbit.ai/code/access-and-billing.md#monthly-spend-cap). |
| **Automation limit** | **Slack** > **Channel mappings**, per assignment | Automation and trigger runs in the matching Slack channels. It's separate from the assignment's **Interactive limit** for runs that people start. A limit of zero blocks new paid runs; trials use their included minutes. See [Spend controls in Slack](https://docs.coderabbit.ai/slack-agent/connections-and-scopes.md#spend-controls). |
| **Automation spend limit** | A scope's spend settings | Automation and trigger runs in the scope, for example in Discord. See [Spend controls in Discord](https://docs.coderabbit.ai/discord-agent/connections-and-scopes.md#spend-controls). |

Channel message triggers on busy channels can start many runs, so give those channels their own limit.

## What's next

> [card] [Automation triggers](https://docs.coderabbit.ai/automations/triggers.md)
>
> Check why a trigger did or didn't start a run.

> [card] [Automation destinations](https://docs.coderabbit.ai/automations/destinations.md)
>
> Change where an automation delivers its results.

> [card] [Automation guides](https://docs.coderabbit.ai/automations/guides.md)
>
> Set up incident response, support triage, ticket triage, and more, step by step.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.