Bot status

Every status a bot can carry, what each one means for your money and your open positions, and what the statuses on its trades, orders and strategy purchases mean.

8 min readUpdated 4 August 2026trading-bot, status, running, stopped, paused, error, limit-reached

Every state a bot and its trades can be in, what each means, and what has happened to your money by the time you see it.

What do DRAFT and RUNNING mean on my bot?

These are the two ends of a bot's ordinary life, and both are on the bot's page under Trading bots (/trading-bot).

DRAFT is a bot that has been created but has never been started. It is not trading, it has placed nothing, and it holds nothing. A bot stays in DRAFT until the first time you press Start, and a bot you take back to draft is treated as being edited — the engine drops it so it cannot keep trading against the old settings. Nothing about a DRAFT bot commits any money.

RUNNING is a bot that is live and cycling. On each cycle it reads the market price, evaluates your strategy, and places, cancels or settles orders as the rules say. This is the only status in which a bot places new orders on its own.

While a bot is RUNNING, its money position is exactly this: nothing is held by the bot, and everything is held by its orders. A live bot's buy orders hold funds out of your wallet the way any order does, and the bot's page shows how much of its allocation those orders and positions currently commit — allocated, in use, and available.

A running bot can be edited only in narrow ways. Its name, description, stop loss and take profit can be changed while it runs; anything else — the strategy, the market, the concurrency and drawdown settings — needs the bot stopped first. A running bot also cannot be deleted.

What does PAUSED mean on my bot?

PAUSED means the bot has been taken out of its cycle. It is not evaluating your strategy and it will not place any new orders while it stays paused.

Pausing is reversible and is meant to be. Resume puts it straight back to RUNNING, and the bot picks up from the current state of the market — it does not replay what it missed. Resuming goes through the same checks as starting, so if you have since hit the cap on how many bots may run at once, or the mode has been switched off at the platform level, the resume is refused for that reason.

What pausing does not reliably do is take the bot's existing work off the market. Orders the bot had already placed can still be resting on the book, and a resting order can still fill while the bot is paused — which means a paused bot can acquire or dispose of a position with nothing evaluating your stop loss over it. Any position it was already holding stays open too. Nothing is sold, nothing is cancelled on your behalf and nothing is returned.

So pause is the right control for "let it sit out the next few cycles". It is the wrong control for "get me out of this market". For that, stop the bot — and if it is holding a position, use Close position as well.

A bot can also be paused by the platform rather than by you. If that happened, the status you will see is LIMIT_REACHED rather than PAUSED.

What does STOPPED mean on my bot?

STOPPED means the bot has been taken out of the market and will not trade again until you start it. It is the normal end state, and it is what you get when you press Stop.

Stopping does two things. It sets the status to STOPPED, and it cancels the bot's working orders — the buys and sells it had resting on the book — so they can no longer fill and whatever they were holding is released back into your available balance. Exit orders already on the book are deliberately left alone, because an exit order is a position on its way out and pulling it would strand the position.

Stopping does not close open positions. This is the thing to be clear about: if the bot had bought and was holding the asset, you still hold that asset after you stop. The order is gone; the position is not. The bot's page will keep showing it, and its cost keeps counting against the bot's allocation, which is why you may find you cannot lower the allocation on a stopped bot.

To actually get out of the position, use Close position on the bot's page. It is a separate control from Stop and it appears whenever the bot is holding something, whether the bot is running or not. On a live bot it sells the whole position at market: a real order goes onto the book, and the position closes when that order fills, so it is not instant. The confirmation says as much before you press it.

The usual sequence is Stop first, then Close position — stopping clears the bot's own orders out of the way so the exit can be sized against the whole position.

My bot says LIMIT_REACHED — what happened?

LIMIT_REACHED means one of the bot's own risk limits was breached and the platform took the bot out of the market for you. It is not an error and nothing has malfunctioned — it is the limit you set doing its job.

Two limits produce it. A daily loss limit, set as an amount or as a share of the bot's equity, is checked as the bot runs; when the day's losses reach it, the bot is pulled. A maximum drawdown watches how far the bot has fallen from its own peak; when it falls that far, the bot is pulled.

What the platform does when that happens, in order: it cancels the bot's working orders so nothing can keep filling, then places a market order to exit everything the bot is holding, and only then writes the LIMIT_REACHED status. Exiting first is deliberate — a bot that stopped without exiting would leave the position open with nothing watching it, which is the opposite of what a loss limit is for.

The exit is a real order, so the position closes when that order fills rather than the instant the limit is hit. If the exit could not be placed at all, the bot's page says so in its error line, and the position is still open and still yours — check it and use Close position if you want it out.

A LIMIT_REACHED bot stays stopped. Nothing restarts it on its own. When you are ready, review the settings that produced it and press Start.

My bot says ERROR — what happened?

ERROR means the bot hit a problem it could not carry on past, so it was taken out of the market. You are sent a notification naming the error, and the bot's page shows the same message in its error line.

The causes are technical rather than financial — the market data the bot needs being unavailable, or the platform refusing an order the strategy tried to place, or a repeated failure in the bot's own cycle. The message on the bot is the specific one, and it is the thing to read first.

An ERROR bot has stopped trading and will not resume on its own. What it does not do is close a position for you. If the bot was holding something when it failed, you still hold it. Open the bot's page and look at what it is holding: if you want that position out, use Close position, which places a real market order to sell it. If it had orders resting on the book, those are pulled when the platform drops the bot.

Once you understand the cause, the bot can be started again from its own page, and starting runs the same checks as any other start.

If the message is one you cannot act on, or the bot goes back to ERROR immediately every time you start it, open a ticket on Support tickets (/support) with the bot's name, its market and the error text shown on the page.

What do the statuses on my bot's trades and orders mean?

A bot's page lists both, and they answer different questions: a trade is a position the bot took, an order is an instruction on the market.

Trades carry one of five statuses. PENDING is a trade being opened. OPEN is a position the bot is holding — this is what counts against the bot's allocation and what Close position acts on. CLOSED is finished, and the row carries the realised profit or loss. CANCELLED means it was ended before it became a position. FAILED means it could not be completed.

Orders carry one of seven. PENDING is an order on its way to the market. OPEN is resting on the book, and while it rests it holds funds. PARTIAL means part of it has traded and the rest is still working. FILLED means it traded in full. CANCELLED means it was pulled — by the bot, by you stopping the bot, or by a risk limit — and whatever it held was released. EXPIRED means the market ended it. FAILED means it never reached the book.

Each order also carries a purpose, which tells you which part of the strategy placed it: ENTRY, EXIT, STOP_LOSS, TAKE_PROFIT, GRID_BUY, GRID_SELL or DCA.

A bot itself carries a mode as well as a status. LIVE means real orders and real money; PAPER means a simulation against a simulated account, where no order reaches the market and no result reaches your wallet.

What do the statuses on a marketplace strategy or purchase mean?

Two different sets, both under Marketplace on Trading bots (/trading-bot).

A purchase — a strategy you bought — carries one of four statuses. COMPLETED is the normal one: the charge went through and the strategy is yours to build bots from. PENDING means the purchase was recorded but has not finished. FAILED means it did not go through. REFUNDED means it was reversed. Only a COMPLETED purchase gives you access, and the platform will not charge you twice for the same strategy — if you already own it, buying again is refused rather than billed.

A strategy you publish yourself moves through its own set. DRAFT is one you are still writing, visible only to you. PENDING_REVIEW is one you have submitted and the platform's reviewers have not yet decided on. APPROVED is live on the marketplace and buyable. REJECTED was not accepted. SUSPENDED was approved but has since been taken down, so it can no longer be bought.

Only a strategy that is both APPROVED and set to public visibility appears on the marketplace at all. A strategy's visibility is either PRIVATE, meaning yours alone, or PUBLIC, meaning offered to others. Strategies also carry a risk level the author declared — LOW, MEDIUM or HIGH — which is a description, not a measurement, and not a statement about what it will do with your money.

If a purchase reads PENDING or FAILED and your balance moved anyway, open a ticket on Support tickets (/support) with the strategy name and the date.