What a DCA bot sends you

DCA bot events arrive in the separate notification bot @Sync_trading_notifications_bot. Without it you will not see a single event: connect it — Main menu → 🔔 Notifications → “Notification chat connected ✅” (see The notification bot).

Where it is in the bot

The delivery mode is the 🔔 Notifications: Realtime button in the bot card; it cycles through Realtime → Every 15 min → Hourly → Daily summary → Errors only. Each bot has its own mode.

How it works

Mode	Ordinary events	Critical ones
Realtime	Collected and sent in a batch roughly every 60 seconds	Immediately
Every 15 min / Hourly / Daily summary	A digest on schedule	Immediately
Errors only	Not delivered; warnings — in a batch once every 24 hours	Immediately

Critical ones are those where a delay costs money: a Stop-Loss, a stop or a pause by a protection, an error, the Kill switch, a position mode change, exchange maintenance, the order limit. Warnings (for example not enough balance) are not lost in the digest even in the "Errors only" mode.

The list of notifications

Ordinary cycle events:

• “🔄 BTC-averaging (BTCUSDT) New cycle #3 started. Bot entered position.”
• “✅ ENTRY order … filled” — the first entry and every averaging buy.
• “✅ Take-Profit hit! PnL: +1.50 USDT” followed by “🎉 Trade finished successfully”.
• With several TP levels: “✅ DCA: TP1/4 BTCUSDT LONG hit at $102.00, partial profit: +2.00 USDT” and after the last one “🎯 All 4 TP orders hit on BTCUSDT/LONG! 💰 Total PnL: …”.
• “🔁 DCA: Take-Profit was cancelled on the exchange outside the bot — placed again for the whole position from the current average entry price.”
• “⏹️ Bot stopped. Reason: stopped by the user” — after ⏹️ Stop.

Critical events and warnings:

• “🔴 Stop-Loss hit. PnL: −7.00 USDT”.
• “🛑 DCA bot #12 was stopped by the system. Reason: 3 stop-losses in a row (limit 3)” — the bot is taken out of service (see Protections).
• “⚠️ DCA bot #12 was paused by the system. Reason: …” — a pause by a protection; the current cycle finishes.
• “⚠️ Could not start a new cycle: … The bot is paused — check the API keys and balance, then tap "▶️ Start".”
• “⚠️ Error: …” — on every failed order placement, for example “Could not connect to the exchange to place the order.”
• “⚠️ DCA: failed to place Stop Loss after ENTRY fill. Reason: …” — the position has no stop, check it on the exchange.
• “⚠️ DCA Flash Warning (BTCUSDT). All 5 entry orders filled within 45 sec.” — a sharp price move, the whole cycle amount is already in the position.
• In SL Timeout mode: “⚠️ Price returned within 12 sec — Stop-Loss did NOT fire (wick protection)” or “🛑 Stop-Loss fired by 30s timeout — position closed at market”.
• “⏳ DCA bot is waiting for start condition over 25 hours” with the buttons 🚀 Start manually and ⏳ Keep waiting — once a day, only for the RSI and SMA conditions.
• After a stop on spot — a message about a coin remainder smaller than the minimum order, with advice to sell it through Convert.

The ones common to all bots — the Kill switch, a position mode change, maintenance, the order limit, a lost connection, a PnL mismatch — are described in the section Notifications and account protection.

Example with numbers

A bot in the "Hourly" mode; within an hour: 3 averaging buys, then a TP of +1.50 USDT and a new cycle. The digest will bring four “✅ ENTRY order … filled”, “✅ Take-Profit hit! PnL: +1.50 USDT”, “🎉 Trade finished successfully” and “🔄 New cycle #4 started” — in a single message at the end of the hour. If a Stop-Loss had fired instead of the TP, “🔴 Stop-Loss hit. PnL: −7.00 USDT” would have arrived at once, without waiting for the digest.

Common errors and what the bot says

• Nothing arrives — the notification bot is not connected or was stopped with the /stop command: open it and send /start.
• Only stops and errors arrive — the "Errors only" mode is on; switch it with the 🔔 button in the card.
• Events arrive with a delay of up to a minute in the "Realtime" mode — that is by design: ordinary events go out in a batch, critical ones immediately.