Why Did My Crypto Trading Bot Stop Trading?
Your bot isn't broken. It's one of five specific, checkable things. Here's how to find which one.
A bot that's gone quiet isn't malfunctioning in some mysterious way — it's one of five specific, checkable conditions, and each one shows up somewhere you can look. This is a different problem from a bot that's trading but not making money; if that's your situation instead, see why your bot shows profit but you still lose money. This is about a bot that isn't placing orders at all.
The five causes, in the order to check them
Insufficient balance
This is the most overlooked cause because nothing about it looks like an error — the bot is connected, the key is valid, permissions are correct, and it still doesn't place the next order. If a DCA bot's next scheduled buy costs more than what's currently available in the funding asset, or a GRID bot's next grid level needs capital that's tied up in other open orders, the bot simply has nothing to execute with. Check your available (not total) balance on the exchange against what the bot's settings call for — total balance can look sufficient while the available portion, after other open orders reserve their share, is not.
API key expired or revoked
Some of this isn't even a failure — it's a security default working as intended. Binance, for instance, automatically disables trading permissions on any API key that isn't restricted to a specific IP address after 90 days, with no warning banner inside the bot itself. If your bot has been running quietly for a few months and then stops with no configuration changes on your end, an auto-expired key is one of the first things worth checking, and adding an IP restriction when you regenerate the key prevents it from happening again. Other exchanges have their own key-lifecycle policies — check your exchange's API management page directly: if the key your bot was using isn't listed anymore, or its permissions have quietly changed, that's the cause. The fix is generating a new key with the same read-and-trade permissions and reconnecting it.
Required permission missing
If the key still exists but was edited to remove trade access — leaving only read — the bot can see your account but can't act on it. This shows up as a bot that appears "connected" without ever placing an order. See what data a trading bot actually needs from an API key to confirm exactly which permissions should be active, and check whether an IP-restriction requirement is what silently dropped the permission in the first place.
Price outside the bot's set range
This is the most common cause for GRID and other range-bound bots specifically: if you set a price range when the market was at one level and it has since moved entirely above or below that range, the bot has nothing left to do inside its own rules. It's not malfunctioning — it's correctly declining to trade outside the boundaries you set, which is the entire point of a range-bound strategy. The fix is adjusting the range to current market conditions, not troubleshooting a fault.
Exchange connection error
Occasionally the issue is neither the key nor the bot's settings — it's the exchange itself, experiencing an outage, maintenance window, or rate-limiting that temporarily blocks API requests. Check the exchange's own status page before assuming the problem is on your end; this resolves itself once the exchange's API is stable again, without any action needed from you.
Working through all five in practice
Check them roughly in the order above: balance first, because it's the fastest to rule out and the easiest to miss; then the key's existence and permissions, since those are binary yes/no checks; then the bot's own range settings against the current market; and finally the exchange's status page, which is outside your control but quick to confirm. Most "my bot stopped trading" situations resolve at one of the first three checks — the fourth and fifth are less common but worth ruling out before assuming something is fundamentally wrong.
If none of these explain it
Confirm the key hasn't been accidentally revoked (see how to check and manage API access), and if the bot still shows no clear cause after checking all five, that's the point to contact support with the bot's ID and a screenshot of its current status rather than continuing to guess.
Four of these five causes are things you set, not things that broke.
FAQ
Why has my trading bot stopped placing orders? Almost always one of five things: insufficient available balance, an expired or revoked API key, a missing trade permission on that key, the market price moving outside the bot's set range, or a temporary exchange connection error.
Can an API key expire automatically without me doing anything? Yes, on some exchanges. Binance, for example, auto-disables trading rights on any key without an IP restriction after 90 days — add an IP restriction when you set up a new key to avoid this.
My exchange balance looks fine — can it still be an insufficient-balance issue? Yes. Check your available balance, not your total balance — funds reserved in other open orders don't count as available, even though they still show in your total.
Is a bot outside its price range broken? No. It's correctly following the boundaries you set. Adjust the range to current market conditions if you want it trading again.
What should I do if I can't find the cause? Rule out all five causes above first, then contact support with your bot's ID and current status rather than continuing to guess.
