Pause, start and stop
A pause does not touch the open cycle, it only forbids starting a new one. Stopping closes the position and ends the bot's work for good.
What it is
| Action | Open cycle | Orders on the exchange | Can it be undone |
|---|---|---|---|
| ⏸️ Pause | Finishes: averaging orders, TP and SL stay | They stay | Yes, with the ▶️ Start button |
| ⏹️ Stop | The position is closed at market | They are cancelled | No — only a new bot |
The pause is the same state the bot enters on its own: by a protection, by the Kill switch, while waiting for an RSI/SMA start condition or for an external signal.
Where it is in the bot
Main menu → 📉 DCA Bots → the bot → ⏸️ Pause, ▶️ Start (shown while paused), ⏹️ Stop. A bot in the “Waiting trigger” status has no pause button — instead there is 🎯 Activate now.
How it works
Pausing during a cycle. The status becomes “Paused”, the position and all orders stay on the exchange, and the TP and SL are moved after averaging buys as usual. If the cycle ends while paused, you get the usual Take-Profit or Stop-Loss notification, the cycle is counted in the statistics, and a new one waits for ▶️ Start.
Starting after a pause:
- the cycle is still open — the bot becomes “Active” again and the cycle continues as it was: no second position and no new entries appear;
- the cycle ended while paused and the cooldown has not expired — the status is “Cooldown”, and the new cycle follows it;
- the cooldown has expired — a new cycle starts at once.
A bot with an RSI/SMA start condition that you paused manually resumes by itself as soon as the condition is met. After the Kill switch, first press 🔄 Reset trigger on the 🛡️ Kill switch screen, then ▶️ Start — the cycle continues from where it stopped.
Stopping. The bot cancels the averaging orders, removes the TP and SL, closes the position at market and sends “⏹️ Bot stopped. Reason: stopped by the user”. On spot some dust may be left — a coin remainder smaller than the minimum order; the bot reports it and suggests selling it through Convert on the exchange (see Spot dust). A stopped bot cannot be started again: the ▶️ Start button works only from the “Created” and “Paused” states, while a bot in “Waiting trigger” is started with 🎯 Activate now.
A slot in the limit. A paused bot keeps taking a slot both in the DCA bot limit (3 by default) and in the plan limit. Only ⏹️ Stop frees the slot. If you delete the exchange bot with the keys, all of its DCA bots will be stopped.
Example with numbers
A Long bot, investment 100 USDT, 60 USDT in the position after the first entry and one averaging buy, cooldown 300 seconds. You pressed ⏸️ Pause at 12:00.
- At 12:20 price reached the TP: “✅ Take-Profit hit! PnL: +0.90 USDT” arrives, and “🔄 Completed cycles” in the card goes up by 1. There is no new cycle — the bot is paused.
- At 12:30 you pressed ▶️ Start: the 300-second cooldown expired long ago, so a new cycle starts at once.
If you had pressed ⏹️ Stop instead of pausing at 12:00, the position would have been closed at market at that same moment — at the current price, not at the TP.
Limits and allowed values
| What | Value |
|---|---|
| States ▶️ Start works from | Created, Paused (“Waiting trigger” uses 🎯 Activate now) |
| A paused bot in the bot limit | Counts |
| A stopped bot | Cannot be resumed; the slot is free |
| Changing parameters while paused | Only the TP strategy and SL Timeout, from the next cycle |
Common errors and what the bot says
- “Bot cannot be activated from state: Stopped” — a stopped bot cannot be brought back; create a new one.
- “Bot cannot be paused from state: …” — pausing is not available, for example on a bot that is already stopped.
- “Bot is already stopped” — ⏹️ Stop was pressed again.
- “Bot is locked by admin: …” — the status is “Locked”, contact support.
- “⚠️ DCA bot #12 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".” — a system pause; fix the cause and press ▶️ Start (see Protections).
- “⚠️ Could not start a new cycle: … The bot is paused — check the API keys and balance, then tap "▶️ Start".” — the cycle start failed, for example because a key was revoked.