Lost connection to the exchange
The bot keeps a permanent connection to Bybit for every exchange bot. If it breaks, the bot reconnects several times in a row by itself, and only when the attempts are used up does it send a warning. Your orders on the exchange keep working all that time.
What it is
The message looks like this:
“⚠️ Bot "Bybit Futures" lost connection to the exchange after 5 reconnection attempts. Check your internet connection and exchange availability.”
The bot here is your exchange bot (the link to the API keys), and the number of attempts is the actual one. This is about the connection between Sync and the exchange, not about your phone: the first thing worth checking is whether the exchange itself is working.
What happens to orders and positions
| What | While there is no connection |
|---|---|
| Orders already placed: entries, Take-Profit, Stop-Loss | Stay on the exchange and are filled by the exchange without the bot |
| Open positions | Stay open; protected by the stops that are already on the exchange |
| New signals from channels | The bot cannot place orders for them until the connection is back |
| Trailing, breakeven, new grid levels, the next DCA order | Do not move and are not placed until it is restored |
This is exactly why a stop-loss has to be on the exchange, not kept in mind: the exchange will execute it itself.
What to do
- Open the Bybit app or website: if the exchange is unavailable or under maintenance, just wait — the bot will connect by itself when the exchange answers.
- If the exchange is working, check the API keys: whether they have expired, whether the key was deleted and whether it has the permissions it needs. See API key permissions, IP whitelist.
- Check the open positions on the exchange by hand: is there a stop, does anything need to be closed manually.
- If the warnings repeat while the exchange is working, write to support.
What happens once it is back
The bot checks every active trade against the exchange and sends the “🔄 Sync after reconnection” report: what filled, what was cancelled, whether the stop was restored. The details are in Restoring after failures. You do not need to do anything special.
Limits and allowed values
| Parameter | Value |
|---|---|
| When the warning arrives | After several failed reconnection attempts in a row; the number of attempts is in the message |
| At what level | For each exchange bot separately |
| What the bot does once the connection is back | Checks the trades against the exchange and sends a report |
Common mistakes and what the bot says
- “⏳ The exchange did not respond within 5 seconds. Try again in a minute — if it keeps happening, the exchange is overloaded or unavailable.” — a one-off delay on your command; repeat later.
- “Could not connect to the exchange to place the order.” — the order was not placed; check the trade card and repeat when the exchange answers.
- “Connection to the exchange failed” — in the reason of a refused trade or level: the same thing, a temporary unavailability.