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

# Rules & Actions Monitoring

> See every rule in your workspace, whoever made it, and every time one ran, and pause any rule that shouldn't be running.

Anyone with access to a workspace can create [rules](https://docs.upsolve.ai/ai-agent-builder/interact/rules-and-actions.md) on their own canvases, including your embedded end users. **Rules & Actions monitoring** is the builder's view across all of them: every rule in the workspace, whoever made it, and every time one ran.

Open it from **Monitoring → Rules & Actions** in the workspace sidebar. It appears once rules are turned on for the workspace (**Workspace settings → Rules & Actions → Allow rules in this workspace**).

![The Rules & Actions monitoring page on the Rules tab, listing each rule with its owner, canvas, type, status and when it last fired](https://mintcdn.com/upsolve/FAICYU48MCHB-H-F/images/ai-agent-builder/improve/rules-oversight.png?fit=max\&auto=format\&n=FAICYU48MCHB-H-F\&q=85\&s=5ebeb3a4e323b8b3672947bcb267c1b3)

## Rules

The **Rules** tab lists every rule in the workspace, most recently changed first:

| Column | What it shows |
| - | - |
| **Owner** | Who made the rule. *Removed user* if they're no longer in the project. |
| **Rule** | The rule's name, and the canvas it's on. |
| **Type** | **Button**, **Schedule**, **Alert** or **Draft**. |
| **Status** | **Enabled**, **Draft**, **Disabled**, or why the rule was paused (below). |
| **Last fired** | When it last ran, or *Never*. |

### Why a rule is paused

Upsolve pauses a rule on its own, and says why in the Status column, when:

* its owner was removed, or hasn't been active for 14 days,
* its owner no longer has access to the canvas the rule reads,
* the canvas or chart the rule reads was removed,
* the connection it sends through needs reconnecting (*Reconnect …*),
* it failed too many times in a row, or
* a builder paused it (*Paused by a builder*).

## Runs

The **Runs** tab lists every time any rule ran, newest first:

| Column | What it shows |
| - | - |
| **Time** | When it ran. |
| **Rule** | The rule, with the error underneath if it failed. |
| **Version** | Which version of the rule ran, for example *v4 · current* or *v2 · deprecated*. |
| **Canvas** | The canvas the rule is on. |
| **Owner** | Who owns the rule. |
| **Triggered by** | Who pressed the button, for a button rule. |
| **Source** | **Schedule**, **Button** or **Test**. |
| **Status** | **Sent**, **Failed**, **Sending**, **Awaiting confirmation**, **Fired**, **Check failed** or **Suppressed** (a limit was reached). For a call to your API, the status code and how long it took. |
| **Destination** | Where it sent: an email address, a Slack channel, an API. |

To see exactly what a run sent (its data, the request and the response, its attachments), the rule's owner opens it from the rule on the canvas. This page shows that a run happened and how it went, not its contents.

![The Runs tab listing each rule run with its time, rule, version, canvas, owner, trigger, source, status and destination](https://mintcdn.com/upsolve/Nurc8hPkBODmwDS1/images/ai-agent-builder/workspaces/rules-monitoring-runs.png?fit=max\&auto=format\&n=Nurc8hPkBODmwDS1\&q=85\&s=6c1184709e95756bd0fc2b9ca30dfb4b)

## Pause a rule

Click **Pause** on any active rule to stop it straight away, for example when it is sending to the wrong place or firing too often. Its status becomes *Paused by a builder*. A paused button stays on its canvas, switched off.

Only the rule's owner can switch it back on, from the rule on their canvas. Owners, admins and members can open this page and pause rules. Read-only members can't open it.

## Next steps

> [card] [Rules & Actions](https://docs.upsolve.ai/ai-agent-builder/interact/rules-and-actions.md)
>
> How rules are created, tested and switched on.

> [card] [API activity](https://docs.upsolve.ai/ai-agent-builder/api-activity.md)
>
> Every write rules and chats sent to your APIs.


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