DN AI Trading Beginner Series · Article 24 · Reviewed 8 November 2026
What matters
Stopping a trading bot does not necessarily cancel orders that already reached the exchange. The bot process, the automation platform and the exchange order book are separate layers. A shutdown in one layer can leave instructions active in another.
If you cannot prove which orders remain live, stop creating new exposure and reconcile the exchange account before restarting the bot.
An “orphan order” is a working order that remains on the exchange after the automation that created or managed it has stopped, disconnected, been disabled or lost track of it. The order may still fill later.
This is a different problem from position drift. Drift is a mismatch between local and exchange state. An orphan order is an instruction that may still change that state in the future.
Why this matters
| What stopped | What may still be live | Risk |
|---|---|---|
| Local bot process | Exchange-native limit/stop orders | Orders can execute while the bot is offline. |
| Webhook receiver | Previously accepted exchange orders | No new signals arrive, but old orders remain. |
| Automation strategy | Existing open positions or working orders | Management logic may stop before the market exposure does. |
| API connection | Orders already accepted by the venue | Revoking access does not necessarily undo prior instructions. |
1. “Stop bot” only blocks new entries
Automation platforms can distinguish between stopping new entries and closing or cancelling existing exposure. Current 3Commas DCA Bot documentation explicitly describes a Stop action that can either leave trades open while monitoring continues or close open positions at market.
The implication is important: “stopped” is not a universal synonym for “all exchange orders cancelled.” Read the exact stop behavior for the strategy you are using.
2. The order already reached the exchange
Once an exchange accepts an order, that order lives in the venue’s own order-management system. Shutting down the strategy that submitted it does not automatically revoke it unless the integration sends a valid cancellation request or the venue has a specific cancel-on-disconnect mechanism configured.
TradingView webhooks illustrate the separation clearly: TradingView sends an HTTP POST to an external endpoint. That delivery is a message to another system, not an ongoing control channel over whatever that system later does on an exchange.
3. The bot lost the cancellation acknowledgement
A bot can send a cancel request and still end up uncertain whether cancellation succeeded. Network timeouts, websocket disconnects or API errors can make the local state say “cancelled” while the exchange still reports the order as working.
The fix is to query the exchange again. Do not infer cancellation from the fact that the local bot stopped displaying the order.
4. Only some orders were cancelled
Strategies can maintain several simultaneous instructions: entries, take-profits, stops, scale-ins, reduce-only orders or multiple grid levels. A shutdown routine that cancels one class of order but misses another leaves residual exposure.
Reconciliation should therefore enumerate every working order on the relevant account and symbol, not just the bot’s preferred order type.
5. A partially filled order still has a remainder
Partial fills create one of the easiest orphan-order traps. Part of the requested quantity becomes a position while the unfilled remainder can remain active unless it is cancelled or the order’s time-in-force removes it.
A bot that records only the filled portion may look “done” even though the exchange still has a live remainder.
6. The platform intentionally unlinked the position or order
Current 3Commas documentation includes an “Unlink & Stop Tracking” action that removes a position from 3Commas without sending an order to the exchange. That is a useful example of why “not visible in the automation interface” is not the same as “gone from the exchange.”
Always distinguish between removing local tracking and changing exchange state.
7. The automation service stopped before the exchange order did
This risk is not hypothetical. During the 3Commas v1 shutdown in September 2026, 3Commas explicitly warned that orders already placed on exchanges would remain live even after v1 automations stopped. The company told users to review and manage open positions and orders directly on their exchanges.
The broader lesson applies to any automation layer: software availability and exchange order state are separate dependencies.
Do not restart first and reconcile later
If you restart a bot while orphan orders are still working, the restarted strategy may create fresh orders without knowing that older instructions can still execute. That can double exposure or produce conflicting exits.
Use the DN Kill-Switch Checklist first, then reconcile current exchange state before re-enabling automation.
DN Orphan Order Recovery Checklist
Tick each item you have independently confirmed at the exchange or authoritative venue API.
This checklist does not connect to an exchange or cancel orders. It is an inspection aid.
A safer shutdown sequence
- Stop new strategy entries.
- Fetch all working orders directly from the exchange.
- Identify which orders belong to the bot.
- Cancel only the orders you intend to remove.
- Re-query until exchange state confirms the cancellations.
- Reconcile current positions and remaining protective orders.
- Only then disable credentials or restart automation.
Tools and platforms
DN currently tracks live automation products including 3Commas and alert workflows from TradingView. Current product behavior can vary by bot type, venue, account mode and configuration, so confirm the exact shutdown semantics before relying on automation.
Affiliate disclosure: Decentralised News may earn a commission from qualifying sign-ups through marked links, at no additional cost to you.
Sources and methodology
- 3Commas — DCA Bot Strategy & Setup Guide
- 3Commas — Positions Tab Overview
- 3Commas — v2 Transition FAQ
- TradingView — Webhook Alerts
Method: DN reviewed current official platform documentation on 8 November 2026 and mapped recurring shutdown/order-state failure modes into a beginner-focused recovery checklist. This article does not inspect any reader account.
FAQ
If I turn off my bot, are all orders cancelled?
Not necessarily. It depends on the platform, bot type and shutdown action. Verify open orders directly at the exchange.
Can an orphan limit order fill hours later?
Yes, if it remains active and its price condition is eventually reached.
Does revoking an API key cancel existing orders?
Do not assume so. Revoking access prevents future API actions, but orders already accepted by the exchange can remain live unless separately cancelled.
What should I do before restarting?
Reconcile working orders, fills and positions first. The restarted bot should begin from confirmed exchange state, not an old local snapshot.
