Your Bot's Trading Pair Is Being Delisted. What Now?
A canceled order leaves your existing coins in the wallet. Follow a practical delisting process: identify the removed product, check each deadline, reconcile balances, and review the next route
An exchange announces that one of your bot's pairs will stop trading. Your bot still holds the coin, several buy orders are open, and the notice mentions more than one deadline.
A trading-pair delisting removes a market; canceling its orders does not sell the assets you already own. Your response starts with identifying what the exchange is removing and ends with reconciling orders, balances, and any remaining route to trade or withdraw.
The word “delisting” can describe a single spot pair, a token across multiple markets, or a derivatives contract. Each requires a different procedure.
First, identify what is being removed
| Announcement | What changes | What to verify |
|---|---|---|
| One spot pair is removed | Trading ends for that base/quote market | Whether either asset still trades through another pair |
| A token is delisted | Multiple markets and other services may be affected | All affected products, deposit status, and withdrawal deadlines |
| A futures contract is removed | The derivative stops trading or settles | Settlement timing, pricing method, and treatment of open positions |
Suppose a fictional COIN/BTC pair is removed while COIN/USDT remains. You may still hold COIN and have a route to trade it. The available quote currency, liquidity, minimum order, and supported bot markets have changed.
By comparison, a token-wide delisting can affect every spot pair on that venue. A futures delisting concerns a contract; holding a derivative does not mean you have a spot token available to withdraw.
Binance's delisting guidance makes the distinction between removing a trading pair and removing the token. Use the specific announcement for the actual assets and schedule.
Read the deadlines as separate events
A trading cutoff, deposit suspension, and withdrawal deadline can fall on different dates. A notice may also specify separate times for margin borrowing, bot services, conversion, or derivatives settlement.
Copy each deadline with its time zone. A notice stating 08:00 UTC refers to 11:00 in Moscow; another exchange may use a different zone. Set reminders against the exact time, leaving room to resolve rejected orders or transfer problems.
Build a short event table:
| Event | What to record |
|---|---|
| Bot or strategy service ends | Exact affected product and the described termination behavior |
| Spot trading stops | Pair, date, time, zone, and open-order treatment |
| Deposits stop | Token, supported network, and deposit deadline |
| Withdrawals stop | Token, network, deadline, minimum, and fee |
| Settlement or conversion occurs | Eligibility, method, and any stated conditions |
Do not assume a deadline absent from the notice. If it covers pair removal alone, check the venue's wallet status and other announcements before concluding that token withdrawals will stop.
Recheck for amendments. Saving the first announcement helps your records, but a newer official update may change the procedure.
Before the trading cutoff: establish the actual inventory
Open the exchange account and identify everything tied to the market: coin balance, quote balance reserved by orders, open limit orders, conditional orders, and relevant bot positions.
A bot's displayed investment can differ from its current holdings. It may have completed cycles, accumulated inventory, or left part of its balance in quote currency. Read the available quantities rather than estimating them from the launch amount.
Also check whether manual trades share the same wallet. Selling the total COIN balance could include assets belonging to another strategy. Record the amount you intend to act on and compare it with the bot's own history.
The general bot-stopped-trading guide helps with balance, connection, and range issues. A confirmed delisting adds an external deadline that those adjustments cannot remove.
Stopping the bot and selling the coin are separate actions
Stopping a strategy can mean canceling its instructions, selling its holdings, or offering a choice between those actions. Check the exact confirmation screen for your platform and bot type.
If the bot stops placing orders but retains the asset, the price exposure remains. If it attempts a market exit, the received price depends on liquidity and any venue limits. During a delisting, the book may be thinner than it was when the bot launched.
After any stop or close action, verify the exchange state. A button press is not evidence that all orders canceled or that a sale completed. Record fills, partially filled quantities, failed requests, and assets still reserved by orders.
Where several tools can place orders in the same account, make sure another strategy cannot submit a new order while you are trying to reconcile the affected pair.
A worked example: 200 coins remain
Consider a hypothetical spot bot holding 200 COIN, with another 100 USDT reserved in unfilled buy orders. You cancel those orders before the market closes.
The cancellation releases the reserved 100 USDT. It leaves the 200 COIN balance unchanged.
| State | COIN held | USDT reserved in the canceled orders |
|---|---|---|
| Before cancellation | 200 | 100 |
| After confirmed cancellation | 200 | 0 |
If COIN/USDT remains available and you choose to sell there, suppose 150 coins fill at 0.50 USDT and 50 fill at 0.46. The gross proceeds are 98 USDT, giving an average sale price of 0.49 USDT before fees.
Multiplying the entire balance by the first displayed price would have suggested 100 USDT. The difference comes from the hypothetical execution prices. An alternative pair provides a trading route; it does not guarantee the same price or reverse the asset's previous decline.
If you retain the coin, record it as an ongoing holding. If you move it, verify the receiving venue, supported network, and current deposit status before sending. A delisting announcement on one venue does not establish that another venue will accept that asset.
Native exchange bots and connected bots can behave differently
An announcement may describe automatic termination of the exchange's own bot product. That statement applies to the named service and event.
A separate platform connected through an API follows its own strategy logic while remaining subject to the exchange's market availability. Do not extend a native bot's automatic-sale or settlement promise to every third-party bot using the same pair.
The same caution applies to pending orders. The exchange may cancel orders at the cutoff, but the announcement's order-cancellation language does not establish what a separate platform will display afterward or whether it will attempt another action.
If the notice and platform instructions leave an uncertainty, use a precise support question: name the venue, pair, bot type, and cutoff, then ask what happens to open orders and held assets. Keep API keys and account secrets out of the message.
After trading stops: reconcile before restarting
Once the market closes, review the final exchange history. Check the last fills, cancellation records, free balances, and any pending withdrawal or settlement.
Save records while they remain easy to access. Keep the bot's configuration and completed-trade history together with exchange exports or transaction references. Those records help explain why the strategy stopped and what happened to its remaining inventory.
A new pair needs a new setup review. Prices expressed in BTC cannot be pasted unchanged into a USDT range. Minimum quantities, precision, spread, and available liquidity can all differ. Starting a replacement bot also creates a new run for your journal, even if it trades the same underlying asset.
If there is no supported trading route, inspect the venue's current withdrawal or settlement instructions. Avoid inventing a conversion deadline or assuming an automatic reimbursement that the announcement does not promise.
Bring orders and balances into one review
Review your trading workflow in Bitsgap
The Bitsgap terminal brings supported exchange markets and orders into one interface. Use it to review the affected strategy alongside the exchange's official notice and final records. Funds remain on your exchange, and its trading, withdrawal, and settlement rules still apply.
Frequently asked questions
Will my bot sell everything when a pair is delisted?
That depends on the exchange announcement and the bot's documented behavior. Order cancellation alone leaves existing asset balances unchanged. Verify the exchange's fills and final balance.
Can I move the bot to another pair?
An alternative pair may provide another route to trade the asset. Check that the platform supports it and rebuild the configuration using its quote currency, liquidity, and order rules.
Does pair delisting mean withdrawals stop?
Removing one pair does not establish that withdrawals will end. Read the token's wallet status and the specific notice for any deposit or withdrawal restrictions.
What happens to a delisted futures position?
The contract's settlement and termination rules determine the outcome. Read the official pricing method, settlement time, and position treatment; spot-token withdrawal instructions do not describe derivatives settlement.
