The bot is not buying: why that happens and what to do

Look at the state first

Every bot in the list says what it is doing now: “Running”, “Paused”, “Stopped”, “Error”, “Emergency stop”. Everything else depends on that.

Whatever has happened to a bot is in the bell at the top of the screen — even with Telegram notifications turned off.

The bot is running but not buying

• The price has not reached a level. A rung buys when the price has come down to its level, not before. In a quiet market a bot can wait for days.
• Every rung has already bought. The bot does not buy below its last rung — it waits to sell.
• The price has left the range. With “Buy only between” set, the grid does not buy outside it, but goes on selling what it holds.
• The price has gone up. A grid that has sold everything waits for a fall from where its last trade closed. If the market keeps rising, it stands without coins. There is a setting for that, “Follow the price up”, and it has its own cost: buying into a rise is dearer if the rise turns.
• The order was not filled. The bot’s order is “fill it whole or cancel it”. On a pair with a thin order book the price can touch the level while the order does not fill.
• A DCA bot buys by the clock, not by the price. Once it has made its set number of purchases it waits for the exit and does not buy until the next cycle.

Buying is paused

“Buying paused” means the bot opens no new positions but sells what it holds. That happens in three cases.

• You chose “Stop buying” yourself. “Resume buying” turns it back.
• The exchange refused an order — there was not enough USDT, say. The bot stops buying and sends the “Buying held” notice. Top the account up and choose “Resume buying”: it does not come back by itself.
• “Buying paused: market crash” is the crash pause of Infinity Grid v2. It lifts by itself once the price stops making new lows.

The exchange holds fewer coins than the bot bought

The bot checks its records against the exchange. If the account holds fewer coins than it bought — you sold them by hand, say, or moved them — it stops buying and says so on its card.

Sold them yourself? Choose “Write off position” and the bot stops counting those coins as its own. Put the coins back and the notice goes away by itself. When several bots on one key trade the same coin they count it together: there may not be enough for all of them at once.

The bot stopped by itself

• “Bot error” — the bot stopped on an error and is not trading. The coins it bought stay in your account.
• “Exchange key rejected” — the exchange no longer accepts the key: it was deleted, say, or its permissions were changed. Bots on that key cannot trade until you replace it. A key that was given withdrawal permission on the exchange is switched off by Nexora itself.
• “Strategy stuck” — the exchange refused orders several times in a row and the bot stopped managing part of the position. Check that the account has the coins and the USDT, and that the pair is trading on the exchange.
• “No price data” — the exchange has not sent prices for the pair for a long time. The bot holds its position but cannot see the market.
• “Subscription ended” — bots stop trading and the coins stay with you. A paid term is followed by three days of grace; a trial has none.

What not to do

• Do not create a new bot on the same pair “just in case”: a grid bot buys its first rung at market the moment it starts, and knows nothing about the coins of the earlier bot.
• Do not sell the bot’s coins on the exchange while it is running: it counts them as its own. If you want out, there is “Sell position”.

If it is still unclear

Write to support from the app — the “Help” section. Name the bot and the time it happened.