“Paused by the system” and “stopped by the system”: the reasons
The bot always names the reason in the message itself. This article is a reference: what every reason means and which button brings the bot back to work.
What it means
Three versions of the message:
- “⚠️ Grid bot #12 was paused by the system. Reason: … Active orders have been cancelled on the exchange. To resume — open the bot in the menu and tap ‘Resume’.” — a hard pause: the orders are removed, the position stays.
- “⚠️ DCA bot #7 was paused by the system. Reason: … The current cycle will complete, new trades will not be opened. To resume — open the bot in the menu and tap ‘▶️ Start’.” — the cycle is finished, a new one will not start.
- “🛑 DCA bot #7 was stopped by the system. Reason: … The bot is taken offline. To start it again — open it in the menu.” — a full stop: the orders are cancelled, the position is closed.
The notification is critical — it arrives immediately in any notification mode.
Why it happens
| Reason in the message | What happened | What to do |
|---|---|---|
| “3 consecutive order placement errors (last: …)” for Grid; for DCA the reason is worded as three order errors in a row (an automatic pause) | Three refusals in a row: not enough balance for Grid, a wrong lot, a revoked key | Remove the cause, then ▶️ Resume / ▶️ Start |
| “3 stop-losses in a row (limit 3)” (DCA) | The limit of stops in a row set by the preset was reached — 3, 4 or 5; a liquidation counts as a stop | A full stop. Review the parameters |
| “leverage 10 × 6 orders = 60 > 50 — the risk is too high” (DCA, futures) | The leverage multiplied by the number of orders is above 50 | Reduce the leverage or the number of orders |
| Delisting of the pair | The exchange removes the pair from trading; a day before the delisting there is a full stop with a close | Nothing can be fixed, the pair is leaving the exchange |
| The position mode was changed | Hedge was switched on at Bybit | See “Position mode changed on the exchange” |
| The subscription is not active (DCA) | A new cycle does not start until the subscription is renewed | 💳 Subscription → renew, then ▶️ Start |
Some things arrive as their own messages: pauses from the protections, “⏸️ … Grid bot paused. Reason: …” (leaving the range, crash protection, margin overload) — see Grid protections and DCA protections; “🚨 KILL SWITCH TRIGGERED” — see Kill switch; “⚠️ Admin action on your bot” — with the action, the reason and who performed it.
What to do
- Read the reason in the message and find it in the table.
- Check the account on Bybit: is there still an open position, are there orders.
- Remove the cause and open the bot card: for Grid — ▶️ Resume, for DCA — ▶️ Start.
- After a message about the bot being stopped by the system you can start it again from its card, but if the reason is in the parameters (stops in a row, leverage × orders) — create a bot with different parameters first: TP, SL, leverage, the amount and the number of orders cannot be changed on a live bot.
When to contact support
If the reason in the message is unclear, or the bot stops again right after a start with no visible reason — write to support: the bot number and the full text of the message.