What arrives immediately
The notification mode governs ordinary events only. Everything where a delay costs money is sent immediately — even if the bot is set to Daily summary or Errors only.
What it is
Every notification has one of three priorities. It decides whether the message goes into the digest and whether the mode can hide it.
| Priority | How it is delivered |
|---|---|
| Critical | Immediately, as a separate message, bypassing the digest and the mode |
| Warning | In the digest on the schedule of the mode; not dropped even in the Errors only mode |
| Ordinary | In the digest; in the Errors only mode it is not shown |
Critical events — always at once
| Event | What the bot sends |
|---|---|
| Liquidation or a forced position reduction by the exchange | “💥 Warning: the exchange is forcibly closing the position. The price reached the liquidation level (or the auto-deleveraging ADL mechanism triggered). Reconciling the trade with the exchange — the outcome will arrive in the next message.” |
| The position is left without protection | “🚨 WARNING: Stop-Loss disappeared from the exchange and could NOT be restored automatically. … The position is currently UNPROTECTED — place a stop manually on the exchange or close the position.” |
| The kill switch fired | “🚨 KILL SWITCH TRIGGERED. All your Grid/DCA bots are paused due to reaching the account-level max drawdown.” |
| The Stop-Loss of a Grid or DCA bot triggered | “🛑 Grid Stop-Loss triggered!” with the price, the trigger type and the realized PnL / “🔴 … Stop-Loss hit. PnL: … USDT” |
| An automatic protection of a Grid or DCA bot fired | “⏸️ … Grid bot paused. Reason: …” — for example, “crash protection: 8 of 20 levels are already in position. All orders were removed, the position is open — check the market and tap "Resume"” |
| A bot error | “⚠️ … Error: …” with the text of the reason |
| A bot was paused or stopped by the system | “⚠️ Grid bot #12 was paused by the system. Reason: …” / “🛑 DCA bot #7 was stopped by the system. Reason: …” |
After reading such a message, open the bot card or the trade card: the message always states the reason and, when needed, what you have to do. The list of Grid and DCA protections is in Grid bot protections and DCA bot protections.
Warnings — not lost
They arrive on the schedule of the mode, but the Errors only mode does not hide them. An example is “⚠️ … Range extension skipped: the price changed by … % in 5 minutes …” for a Grid bot with trailing: the pump protection did not let the grid expand, the bot keeps working.
Other important alerts
They concern the account or the exchange bot as a whole, not one Grid or DCA bot, so they are not tied to the notification mode and arrive at once:
- “🚨 Position mode changed on the exchange” — the bot is paused until you set One-Way back and unpause it;
- “⚠️ Exchange scheduled maintenance” — with the start time and the list of affected pairs (see Exchange maintenance);
- “⚠️ You are using 410 of 500 active orders on the exchange (82%)…” — Exchange order limit;
- “⚠️ Bot "…" lost connection to the exchange after … reconnection attempts” — Lost connection to the exchange;
- “⚠️ PnL mismatch detected” — PnL mismatch;
- “🔄 Sync after reconnection” — Restoring after failures;
- an administrator action on your bot — with the action, the reason and the administrator.
Ordinary events — by the mode
A grid level filled (“💰 … filled at price …. Profit: … USDT”), a DCA cycle started (“🔄 … New cycle #3 started. Bot entered position.”), a Take-Profit hit, the daily summary (“📊 … Daily summary: 14 trades, Day PnL: … USDT”), messages about the progress of order placement. In the Errors only mode you will not see them — look at the bot card.
Limits and allowed values
| What | Value |
|---|---|
| Priorities | 3: critical · warning · ordinary |
| Can critical ones be switched off | There is no separate setting; they stop only when the notification chat is off (/stop) |
| Who sets the priority | The bot, by the type of event; it cannot be configured by hand |