> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/dashboard-and-account/notifications-and-alerts.md).

# Notifications and alerts

Surge tells you about important events in three ways: **in-app notifications** (the bell in the header), **email** (for strategy warnings, once you verify an address), and **toasts** for live events while the tab is open. Browser push notifications can be enabled in Settings, but `[VERIFY: the current build registers a placeholder device token, so push messages are not actually delivered]`.

### In-app notifications

The bell shows two tabs: **Notifications** (persisted messages from Surge) and **System alerts** (live health issues). Unread state is tracked per notification in this browser. Messages you will see:

| Event                                         | Message                 |
| --------------------------------------------- | ----------------------- |
| Login                                         | Sign-in alert           |
| Email added or verified                       | Confirmation            |
| Staking epoch finalised with a reward for you | "New rewards available" |
| Staking payout sent                           | "Rewards sent"          |
| Cadence order failed 5 times                  | Strategy warning        |
| Broadcasts from Surge                         | Announcements           |

### Email

Settings → General → Notification settings. Enter an email, receive a 5-digit code (valid 5 minutes), enter it to verify. Verified emails receive **strategy warning** emails — for example when a Cadence order has failed repeatedly. Unsubscribe removes the address.

### Toasts and live events

While the tab is open, Surge shows toasts for order confirmations (only for transactions you placed), strategy errors, an arbitrage strategy stopped by its risk limits, signing prompts, session expiry, and network or socket problems. A **socket status pill** in the header aggregates the health of the live channels (price feed, each strategy type, transactions); hover for per-channel detail. The price chart shows LIVE / STALE / RECONNECTING / OFFLINE for the price feed.

### System alerts

Derived from live state and shown on the dashboard and in the bell's System alerts tab: strategy execution errors, per-strategy arbitrage connection errors, unexpected pauses, a strategy wallet under 5 ADA, balance-lookup failures, strategy conflicts, failed orders. They clear when the condition clears.

### What Surge does not notify

* A strategy that stopped trading because the tab was closed (Cadence skips orders silently).
* Grid or rule-based pauses (visible only on the strategy page and dashboard).
* Fills — check the trade log or the transaction toast.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.surgecardano.com/dashboard-and-account/notifications-and-alerts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
