Protections: consecutive stops, leverage × orders, a series of errors
A DCA bot watches not only the price but also its own results. If the market moves steadily against the strategy or the exchange rejects orders, the bot stops or pauses itself and sends the reason.
What it is
| Protection | Condition | What the bot does |
|---|---|---|
| Consecutive stops | M stop-losses fired in a row: 3 / 4 / 5 depending on the preset; liquidation counts as a stop | A full stop: orders cancelled, position closed |
| Leverage × orders | Leverage × number of orders above 50 (futures only) | At creation — refusal; on a running bot a check every 2 minutes → pause |
| Series of errors | 3 failed order placements in a row: a revoked key, a pair delisted from trading, a wrong lot step | A pause with the reason; the current cycle finishes |
| DCA Flash Warning | At least 3 fills and all averaging orders of the cycle filled in under 2 minutes | A warning only, the bot keeps working; checked every 2 minutes, once per cycle |
| Kill switch | Account drawdown reaching the set limit | A pause, including for bots waiting for a trigger; the current cycle finishes |
| Position mode changed | Hedge is switched on at the exchange instead of One-Way | A pause; restore One-Way and press ▶️ Start |
| The pair is being delisted | Checked once an hour | A pause; one day before the delisting — a stop with the position closed |
| A forgotten cycle | A cycle with no changes for 14 days | Cancellation and a notification |
| Subscription is not active | The trial, the paid or the grace period has ended | No new cycle starts, the bot is paused |
Not having enough balance for the next averaging order is not treated as an error: the bot waits, the skipped order is retried on the next fill, and the TP stays in place.
The consecutive-stops counter is visible in the card as the line “⚠️ Consecutive SL: 2 / 4” and is reset by any cycle that did not end with a stop. The number M is set by the preset (🛡️ Conservative — 3, ⚖️ Standard — 4, 🚀 Aggressive — 5) and cannot be changed in the wizard.
Where it is in the bot
The protections need no setup — they always work. The Kill switch is enabled separately: Main menu → 🛡️ Kill switch (see Kill switch: drawdown protection). The bot sends the reason for a stop or a pause into the notification chat; the status is visible in the card.
How it works
A stop (consecutive stops, a pair being delisted) is final: orders cancelled, position closed, the bot is in the “Stopped” status. After that — a new bot with different parameters.
A pause (leverage × orders, a series of errors, the Kill switch, position mode, subscription) is reversible: the current cycle finishes with its own TP and SL, and no new cycles are opened. Once the cause is fixed, press ▶️ Start in the card. After the Kill switch, first press 🔄 Reset trigger on its screen.
Example with numbers
Preset ⚖️ Standard (limit of 4 consecutive stops), SL 7 %, investment 100 USDT. Cycle 1 — TP, cycle 2 — SL (counter 1 / 4), cycle 3 — SL (2 / 4), cycle 4 — TP (counter reset), cycles 5-8 — four stops in a row. After the fourth one you get “🛑 DCA bot #12 was stopped by the system. Reason: 4 stop-losses in a row (limit 4)”. The loss of the series is about 4 × 7 USDT = 28 USDT plus fees; without the protection the bot would have kept opening cycles in a falling market.
Leverage × orders: x10 and 6 orders = 60 > 50 — the bot refuses at creation; x5 and 10 orders = 50 is allowed.
Limits and allowed values
| Parameter | Value |
|---|---|
| Consecutive stops before the bot stops | 3 / 4 / 5 depending on the preset |
| Leverage × orders | no more than 50 |
| Consecutive order errors before a pause | 3 |
| Flash Warning | all averaging orders in under 2 minutes, from 3 fills |
| A forgotten cycle | 14 days without changes |
Common errors and what the bot says
- “🛑 DCA bot #12 was stopped by the system. Reason: 3 stop-losses in a row (limit 3)” — the market is against the strategy; reconsider the pair, the direction or the averaging step before creating a new bot.
- “⚠️ DCA bot #12 was paused by the system. Reason: leverage 10 × 6 orders = 60 > 50 — the risk is too high. Reduce the leverage or the number of orders and start the bot again” — that combination almost certainly leads to liquidation if price moves against the position.
- A system pause with a reason saying that three order errors in a row triggered an automatic pause. Before it, every failure was reported as “Could not connect to the exchange to place the order.” Check the keys and the pair, then press ▶️ Start.
- “⚠️ DCA Flash Warning (BTCUSDT). All 5 entry orders filled within 45 sec. This may indicate a flash crash or sudden price movement. Please review your position and adjust bot parameters if needed.” — the bot keeps working, but the whole cycle amount is already in the position.
- “🚨 KILL SWITCH TRIGGERED. All your Grid/DCA bots are paused due to reaching the account-level max drawdown.” — see How to reset the trigger.
- “🚨 Position mode changed on the exchange. DCA bot #12 (BTCUSDT) has been paused. Expected: One-Way. Actual: Hedge.” — see “Position mode changed on the exchange”.
- “🛑 The grace period is over — view-only mode is on. New trades are not opened, DCA and Grid bots are paused.” — renew the subscription in the 💳 Subscription menu.