> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ansio.trade/llms.txt
> Use this file to discover all available pages before exploring further.

# Find a bot error

> Open the error guide for your ANSIO bot. Find exact messages, waiting states, stopped strategies, rejected orders and the records needed to investigate them.

Choose the affected strategy. One bot can stop while others on the same account keep running.

> [card] [Spot MM](https://docs.ansio.trade/spot/mm-errors.md)
>
> Balance-change guards, insufficient funds, price sources, precision, exchange minimums and missing levels.

> [card] [Spread](https://docs.ansio.trade/spot/spread-errors.md)
>
> Lost-order counts, breach warnings, Oversold, side modes and missing quotes.

> [card] [Equaller](https://docs.ansio.trade/spot/equaller-errors.md)
>
> Run allowances, free funds, deviation tolerance, rejected sizes and what a restart resets.

> [card] [Cashout](https://docs.ansio.trade/spot/cashout-errors.md)
>
> Price floors, daily limits, precision, safe pricing, token balances and synced waiting.

> [card] [Futures MM](https://docs.ansio.trade/futures/errors.md)
>
> Margin waits, position allocation, blocked quotes, stale data, liquidation alerts and rejected settings.

> [card] [Autopilot](https://docs.ansio.trade/autopilot/errors.md)
>
> Expired proposals, permissions, scheduling, unsupported changes and pending verification.

## Read the current state

| State | What to establish |
| - | - |
| Running, no new order | The bot may be waiting for funds, a price or an available allocation. Read its waiting reason. |
| Exited | Read the strategy exit record and what happened to remaining orders. An exit does not prove that every order was cancelled. |
| Previous strategy error | Compare its timestamp with the current run. It can be historical. |
| No quote or stale data | A value is unavailable or outdated. It is not zero. |
| Pending settings | The slider value may not yet be applied. Read the result of Save & Restart where required. |

## Find the exact record

Open the account's **Strategy** log around the time of the issue. Use **Fills** to see actual executions; an open order and a fill are different records.

![ANSIO Strategy log with timestamps and tabs for Fills and PnL.](https://mintcdn.com/ansio/TbUlSsAFRzZei_af/images/docs/logs.jpg?fit=max\&auto=format\&n=TbUlSsAFRzZei_af\&q=85\&s=3137cb23dd6ef0e42f87ae449bac5b49)

The native account log with demonstration events.

Read the full message, affected side, limit and order-handling detail. The short error label can omit that context.

## An error did not produce an alert

Each rule has its own first-alert delay. For example, an exited strategy must remain down for ten minutes before its down alert fires. A brief error can appear in the log without becoming a notification.

Open [Alerts](https://docs.ansio.trade/alerts/overview.md), [rule timing](https://docs.ansio.trade/alerts/rules.md) or [delivery troubleshooting](https://docs.ansio.trade/alerts/delivery.md).

## A settings change did not take effect

Some controls hold pending values until **Save & Restart**. Read the applied configuration and the action result afterward. Spot **PnL mode** is an exception: its tracking toggle takes effect without a restart.

Restarting can reset a run allowance, particularly for Equaller. It is an execution action, not a refresh button.

## If the cause is still unclear

Send [Support](https://docs.ansio.trade/support.md) the client, exchange, pair, bot, exact message, time and timezone. Include the last action or setting you changed and a relevant screenshot.

Leave API secrets out. If an exchange action has an uncertain result, establish the current orders and position before submitting it again. See [connection and data issues](https://docs.ansio.trade/troubleshooting/connections.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.