Notification modes and the digest
Grid and DCA bots produce a lot of events: a level filled, a cycle started, a take-profit hit. So that the notification chat does not turn into a feed, every such bot has its own mode: receive everything at once, in batches for a period (a digest) or only problems.
What it is
A digest is one message with the list of events for a period instead of a separate message for each of them. The mode is set for every Grid and DCA bot separately: a calm grid can stay on Daily summary, while a new bot you are watching is better on Realtime.
| Mode | What arrives |
|---|---|
| Realtime | Events arrive at once; ordinary events that happened within the same minute may arrive in one message |
| Every 15 min | A digest for 15 minutes |
| Hourly | A digest for an hour |
| Daily summary | One summary a day |
| Errors only | Problem events only |
Where it is in the bot
- Grid: Main menu → 🪜 Grid Bots → the bot → the 🔔 Notifications: Realtime button.
- DCA: Main menu → 📉 DCA Bots → the bot → the same 🔔 Notifications: … button.
The button always shows the current mode of the bot. Tapping it switches the mode.
How it works
Not every event obeys the mode. Each notification has a priority:
| Priority | Behavior | Examples |
|---|---|---|
| Critical | Arrives immediately, bypassing the digest and the mode | Liquidation, a position left without a stop-loss, the kill switch fired, a bot protection fired |
| Warning | Goes into the digest, but is not dropped even in the Errors only mode | A skipped range extension of a Grid bot with trailing (pump protection) |
| Ordinary | Goes into the digest; in the Errors only mode it is not shown | A grid level filled, a DCA cycle started, the daily summary |
The mode applies only to the events of the Grid or DCA bot itself. Account-wide alerts — exchange maintenance, a position mode change, the order limit, the kill switch, a lost connection to the exchange — are not tied to the mode and arrive immediately.
The full list of what arrives immediately is in the article What arrives immediately.
Example
A Grid bot on BTCUSDT is switched to Every 15 min. Six levels filled within that quarter of an hour — you get one message with all six fills and the profit of each. If the crash protection fires within the same 15 minutes, its message arrives at once, separately, without waiting for the digest.
The same bot in the Errors only mode: level fills do not arrive at all, while a protection that fired arrives immediately. A warning about exchange maintenance arrives at once in any mode: it concerns the account, not this bot.
Which mode to choose
- Realtime — the first days of a bot, when it matters to see every action.
- Hourly or Daily summary — a grid with many levels on a moving pair: there are many events and you do not need to react to each of them.
- Errors only — if you have several bots and want to see only what needs attention. Ordinary events (fills, the PnL of the day) will not arrive — look at them in the bot card.
Limits and allowed values
| Parameter | Value |
|---|---|
| Modes | 5: Realtime · Every 15 min · Hourly · Daily summary · Errors only |
| Where it is set | In the card of each Grid and DCA bot separately |
| What does not depend on the mode | Critical events — always immediately |
| What is not lost in Errors only | Warnings |
The mode affects the notifications of Grid and DCA bots only. The notification bot must be connected first — otherwise nothing arrives in any mode.