A trading bot relies on the local network environment and program process. Once the internet connection drops or the client shuts down abnormally, the bot itself will not execute any new operations automatically. Any unfulfilled pending orders remain on the exchange, but the system will no longer generate new orders based on market changes.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Below are three steps to confirm and remedy after the bot loses connection.
Step 1: Verify the Real Status — Check Positions and Pending Orders on the Exchange Side
After disconnection, the bot's display may freeze, but that does not reflect the real state of the exchange servers. You must verify through official channels first.
What to do: Do not rely on the bot interface. Log in to the exchange's official website or app directly to view actual positions and pending orders.
How to do it:
Situation A (using mobile): Open the exchange app, go to "Futures" or "Spot" account, and check "Current Positions" and "Current Orders." If the market was volatile, some pending orders might have already been filled.
Situation B (using desktop): Try reopening the trading platform webpage, log in, and check the same information. If the network has recovered but the page loads abnormally, check your local network connection first.
When is this step complete: You clearly know what positions you actually hold and which pending orders are still on the order book. This is the basis for all subsequent actions.
Common failure reason: Assuming everything is fine because the bot interface shows "Running." The bot's interface might be stuck at the state before disconnection; the exchange side prices and order statuses may have changed completely.
Risk reminder: If the price hit your stop‑loss or take‑profit orders during the disconnection, those orders will execute automatically on the exchange server and will not expire just because your bot is offline. The first thing after logging in is to check your balance changes.
Step 2: Assess the Bot's "Leftover Tasks" — Which Ones Need Manual Takeover
During the disconnection, the bot may have missed entry or exit signals because it could not get market data. These unexecuted tasks need you to take over manually.
What to do: Check the bot's logs or strategy settings to identify conditions that should have triggered but didn't during the disconnection.
How to do it:
Review the trigger conditions set in the bot's strategy (e.g., "open position when price falls below a moving average" or "close position when RSI is overbought").
Compare the current market price with the price range during the disconnection and determine if a signal occurred but was not executed.
If the condition is still met and you agree with the signal, manually execute the corresponding opening or closing trade.
If the condition has passed (the price has already reversed), scrap that part of the task; do not "catch up."
When is this step complete: You have checked every trigger condition in the bot's preset strategy one by one and made a manual judgment on whether to execute each qualifying signal.
This is where the main risk of local algorithmic orders lies: they rely on your local market data and network to trigger. When the software closes or the network disconnects, these algorithms stop working completely.
Step 3: Set Temporary Risk Controls — Prevent "Recovery Anomalies"
When the network recovers and the bot reconnects, it may receive a flood of backlogged market data instantly, leading to abnormal signal judgments or even batch order placements.
What to do: Before restoring the bot to normal operation, manually restrict its trading permissions.
How to do it:
If the bot supports a "monitor only, no trading" mode, switch to that mode first. Observe a few market cycles before turning the trading function back on.
If the platform supports it, temporarily disable the "order" permission in the API settings, keeping only "read" permission. Re‑authorize after confirming the data stream is normal.
Check the current available margin in your account. If any positions were force‑liquidated or partially filled during the disconnection, the reserved margin may be insufficient to support subsequent operations; you may need to top up or reduce positions first.
When is this step complete: You have confirmed that the bot will not send a bunch of unexpected orders instantly due to data backlog after recovery. A limit‑order worker lacking a retry‑on‑failure mechanism may permanently disable an order after a single temporary glitch.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
How to Confirm the Operations Are Correct?
After the network recovers, go through all three steps. Finally, verify: the account positions and pending orders match your actual intent; any signals missed during the disconnection have been handled manually; the bot is in a controlled state. For future prevention, it is recommended to prioritize server‑side conditional orders (like stop‑loss and take‑profit orders) provided by the trading platform. These orders are stored on the exchange server and are unaffected by local disconnection. If you must use a local bot, pay attention to error codes such as "connection lost" and "timeout" in the API configuration as a reference for fault monitoring.
