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

# Use the Alerts tab

> Read open and resolved incidents, filter by client and pair, understand Acknowledge and Snooze, and find the settings behind a notification.

Open **Alerts** in the ANSIO desk. It brings together bot stops, balance and position limits, price-source failures, Autopilot recommendations and connection problems.

An alert describes a condition. It does not, by itself, change a bot setting or close a position.

## Find the affected account

**1. Choose the scope**

Use **All clients**, **All pairs** and **All alerts** to narrow the list. **Clear filters** restores the full view available to your role.

**2. Read Open or Resolved**

**Open** contains active incidents, including ones that have been acknowledged or snoozed. **Resolved** contains conditions that have cleared.

**3. Read the card**

Start with the client, pair, exchange, severity and time. Read the detail for the affected strategy, current value and limit.

**4. Open the account**

Compare the incident with current settings, balances, orders and the strategy log. Use the bot-specific error guide if it stopped.

The navigation count includes open incidents even when they are snoozed. If the alert data cannot be loaded, a missing count is not evidence that the desk has no problems.

## Categories

| Category | Examples |
| - | - |
| Spot | An exited strategy, an empty book side, balance floors, Spread breaches, Equaller allowances and blocked Cashout. |
| Futures | Blocked quotes, low available margin, stale position data and liquidation distance. |
| Rates | A missing source, a frozen reference or a change to Market. |
| Autopilot | Recommendations awaiting review or a contract it cannot hold within the permitted settings. |
| Infrastructure | An unavailable venue or a trading service that is not reporting. |

Expand the relevant category to read its rules. **Waits** is the delay before the first alert; **Reminds** controls later notifications. They are separate settings.

## Acknowledge and Snooze

| Action | What it does |
| - | - |
| **Acknowledge / Ack** in Telegram | Records who has seen the incident. It does not disable reminders. |
| **Snooze 10m / 1h** in Telegram | Postpones notifications for that incident. |
| **Quiet for 1h / 4h** in the desk | Acknowledges and snoozes the incident for that period. |
| Personal rule set to **Off** | Stops that rule's notifications for the selected recipient. It does not remove the desk incident. |
| Personal **Reminds = 0** | Allows the first notification but disables ordinary repeats for that recipient and rule. |

Acknowledgement and snooze belong to the shared incident. Recipient severity, reminder interval and delivery schedule are personal.

Snoozing leaves the underlying problem in **Open**. A severity escalation can produce a new notification and end the incident's snooze.

## When an alert becomes Resolved

For condition-based incidents, the condition must clear and remain clear for **60 seconds** before resolution. Some rules also require a recovery margin, such as liquidation distance recovering to 20%.

Missing or failed observations do not prove recovery. ANSIO keeps the last known incident instead of treating unavailable data as a healthy account.

A resolved notification is sent only for an alert episode that the recipient previously received. Delivery settings still apply.

## In Telegram

![Telegram alerts showing a low-margin incident, a resolved message and blocked Futures quotes.](https://mintcdn.com/ansio/TbUlSsAFRzZei_af/images/docs/telegram-alerts.png?fit=max\&auto=format\&n=TbUlSsAFRzZei_af\&q=85\&s=2f07035ae70ed00d3e9a0070a190d678)

ANSIO Telegram alerts from the landing-page demonstration. Acknowledge and Snooze are beneath each active message.

Read the **High / Critical / Resolved** state before acting on an older message. Open the current account when the message and the desk no longer show the same condition.

> [card] [Timing and delivery](https://docs.ansio.trade/alerts/delivery.md)
>
> First alerts, repeats, schedules, vacation pauses and missing messages.

> [card] [Rule reference](https://docs.ansio.trade/alerts/rules.md)
>
> The condition, first-alert wait and scope for each rule.

> [card] [Bot errors](https://docs.ansio.trade/troubleshooting/orders.md)
>
> Separate guides for MM, Spread, Equaller, Cashout, Futures and Autopilot.

> [card] [Telegram controls](https://docs.ansio.trade/telegram/controls.md)
>
> Account views, commands and confirmed actions.


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