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

# Notifications

> Email and Telegram alerts for budget pauses and finished Hive Agent runs

Hive Agents can send three kinds of dashboard alerts. All three reuse the same **Notifications** delivery settings on the Hive Agent blueprint: **Send via** (Email or Telegram), optional **Email address**, and optional **Telegram account**.

These alerts are separate from [public API callbacks](./invoke-from-code). Callbacks are HTTPS webhooks for code integrations. Dashboard notifications are email or Telegram messages for people working in Fetch Hive.

## Comparison <a href="#comparison" id="comparison" />

| Alert                    | When it sends                                                                          | Opt-in?                                         | Link in message                                             |
| ------------------------ | -------------------------------------------------------------------------------------- | ----------------------------------------------- | ----------------------------------------------------------- |
| **Budget hint approval** | Run pauses after crossing **Budget Hint** under conservative or balanced strictness    | Always when the run pauses                      | Magic link to the [budget approval](./budget-approval) page |
| **Hard cap approval**    | Run pauses at **Budget Cap** when **When hard cap is reached** is **Ask for approval** | Always when the run pauses                      | Same magic-link approval page                               |
| **Run finished**         | Run reaches `completed`, `failed`, or `cancelled`                                      | Off by default; enable per blueprint or per run | Deep link to the run in [Logs](./logs)                      |

Fetch Hive does not send a separate in-app bell notification for Hive Agent runs today.

## Who receives alerts? <a href="#recipients" id="recipients" />

**Budget approvals** go to the Hive Agent creator when that person is still an account member. If not, Fetch Hive uses the account owner.

**Run finished** alerts prefer the dashboard user who started the run. If the run was started without a user (for example from the public API), Fetch Hive falls back to the same creator → account owner rule.

If **Email address** is set under **Notifications**, alerts go there. Otherwise Fetch Hive uses the resolved recipient's account email.

## Configure delivery <a href="#configure-delivery" id="configure-delivery" />

Open the Hive Agent editor and click the bell button in the editor control bar to open **Notifications**.

* **Notify when run finishes** — task-level default for run-finished alerts (off by default)
* **Send via** — **Email** or **Telegram**
* **Email address** or **Telegram account** — optional override for where alerts are delivered

If **Send via** is **Telegram** but no active Telegram destination is available, Fetch Hive falls back to email.

See [Creating and Configuring](./creating-and-configuring) for the Budget Settings and Notifications controls.

## Budget hint approval <a href="#budget-hint-approval" id="budget-hint-approval" />

This alert fires when a run crosses the **Budget Hint (USD)** and Fetch Hive pauses for human review.

Typical causes:

* **Budget Strictness** is **Conservative** — Fetch Hive pauses soon after the hint is crossed
* **Budget Strictness** is **Balanced** — the run may continue with lower concurrency first, then pause if spending keeps rising

The message summarizes spend against the hint. **Additional budget (USD)** is optional on the approval page.

While waiting, the run status is `blocked`. See [Budget Approval](./budget-approval) for approve, decline, expiry, and resend behavior.

## Hard cap approval <a href="#hard-cap-approval" id="hard-cap-approval" />

This alert fires when cumulative spend plus projected next gated work reaches the **Budget Cap (USD)** and **When hard cap is reached** is set to **Ask for approval** instead of **Stop run**.

The message includes:

* Spend so far against the hard cap
* Estimated cost for the next gated work
* A suggested additional budget amount

**Additional budget (USD)** is required on the approval page for hard-cap pauses.

Approval raises the cap by the amount you enter, then budget is checked again before work continues. If the amount is too low, the run can pause again.

## Run finished <a href="#run-finished" id="run-finished" />

This alert fires when a run reaches a terminal status:

* `completed`
* `failed`
* `cancelled`

It does **not** fire when a run is `blocked` waiting for budget approval — the budget approval alert already went out.

### Task default

In **Notifications**, turn on **Notify when run finishes** to make this the default for future dashboard runs.

### Per-run override

In **Start Run**, use **Notify me when this run finishes** to override the task default for one execution. See [Running Tasks](./running-tasks).

The message includes the Hive Agent name, objective, terminal status, total spend, and a link to open the run log.

## What is not covered here <a href="#not-covered" id="not-covered" />

* **In-app notification bell** — Hive Agent runs do not create bell notifications today
* **Public API callbacks** — use `async.callback_url` on [Invoke from Code](./invoke-from-code); inspect delivery in [Logs](./logs)
* **Live dashboard updates** — the editor and logs pages still update over websockets while a run is in progress; that is not an email or Telegram alert

See also: [Budget Approval](./budget-approval), [Running Tasks](./running-tasks), and [Logs](./logs).