Could not place Stop Loss
The stop is the one order without which a position is left unprotected, so the bot reports any problem with it immediately and tells you what to do.
What it means
| Message | What the bot did |
|---|---|
| “🛡️ The exchange could not place Stop Loss. Position closed at market for protection. Trade finished.” | A signal trade: the stop did not go in after the entry — the bot closed the position so as not to hold it unprotected |
| “⚠️ DCA: failed to place Stop Loss after ENTRY fill. Reason: … What to do: check position on the exchange and cancel the trade manually if needed. SL will be re-attempted on the next ENTRY fill.” | DCA: the position is not closed, a new attempt at the next fill |
| “🛡️ Stop-Loss disappeared from the exchange (removed manually or cancelled) while the position was open. The bot restored protection: stop at 58000, size 0.1. The position is protected again.” | It put the stop back itself |
| “🚨 WARNING: Stop-Loss disappeared from the exchange and could NOT be restored automatically. Reason: … The position is currently UNPROTECTED — place a stop manually on the exchange or close the position.” | Critical: your action is needed |
| “⚠️ Stop order was not executed and was cancelled by the exchange. Price has already passed the SL level.” | The exchange found no volume at the stop price; the position is open, the bot will offer options |
| “After restart an open position without stop-loss was detected, and no default SL is configured for the bot. Please set a stop-loss manually or close the position.” | There is nothing to restore from: the settings have no default stop |
Do not confuse this with normal behavior: for a Grid bot and for DCA in SL Timeout mode the stop is not visible on the exchange — the bot runs it; on futures, Positions → TP/SL only holds the safety stop near the liquidation.
Why it happens
- The price has already passed the stop level: “Could not place Stop Loss. The specified price is on the wrong side of the current price. Stop Loss must be below the current price for LONG, and above for SHORT.”
- The limit of conditional orders on the exchange is used up: “⚠️ Exceeded the limit of conditional (stop) orders for this symbol.”
- The stop was removed by hand on Bybit.
- There was no connection to the exchange, or the keys stopped being accepted.
- The settings say to trade without a stop — then the bot warns: “Warning: the signal trade was opened WITHOUT a stop-loss (bot is configured to trade without SL). Liquidation risk — monitor the position manually.”
What to do
- Open the position on Bybit and see whether it has a stop. If the message says the position is unprotected — place a stop by hand right away or close the position.
- If the exchange removed the stop because the price had already passed the level — place a new one a little further from the current price from the trade card, or close the position fully or partially.
- If the trade is in an unusual state, Retry execution appears in its card — the bot will offer to place the SL again itself.
- Check the trading settings: turn on a default stop so the bot always has something to protect the position with, and the policy for a signal without SL.
- Do not remove the bot's stops on the exchange by hand: the bot will restore them, and if it cannot, the position is left unprotected.
When to contact support
If the stop cannot be placed repeatedly while the price is normal and the order limit is free, or the bot closed a trade for protection with no visible reason — write to support: the trade number, the time and the text of the message.