> ## 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.

# Spread errors

> Understand lost-order limits, Spread warnings, insufficient funds, oversold errors and missing bid or ask quotes.

Spread has its own limits and can stop while another bot on the account keeps running. Read the **SPR** strategy record, not just the account's overall status.

![Spread lost-orders error card with its breach count in the ANSIO demo.](https://mintcdn.com/ansio/TbUlSsAFRzZei_af/images/docs/spreadCrop.jpg?fit=max\&auto=format\&n=TbUlSsAFRzZei_af\&q=85\&s=3ea9dcd7033353fee1f3b67f879aae40)

Spread's lost-order guard, shown with demonstration data.

## Orders has been lost too many times

This is the wording used by the error card. The raw message may read `Orders has been lost N times`.

The bot reached its **Max lost orders** guard after repeated maximum-spread breaches. The count is a strategy limit; it is not a count of all trades or a claim that the exchange lost your order history.

Compare the recorded count with **Max lost orders**, the affected side, the reference and **Max spread**. Read the exit record for what happened to remaining orders. Restarting without addressing the cause can lead to the same stop.

## Spread bot is losing orders

This is an advance warning in **Alerts**, rather than the final exit. It becomes eligible when the breach count reaches 70% of the allowed maximum, rounded up.

For a maximum of 10, the warning threshold is 7. Read the count and recent market movement before changing either limit. Increasing the allowed count lets the bot tolerate more breaches.

## Oversold

An `Oversold` message can mean the requested sale exceeds the usable token balance or the amount available under the strategy's allocation. It does not, by itself, mean a leveraged short position was opened.

Compare available tokens with tokens reserved by MM, Spread and other sell orders on the same account. Use the full error detail to identify the side and amount.

## Balance not enough

For `Balance not enough` or `Insufficient account balance`, compare the order with free funds on that side. Quote currency funds bids; tokens fund asks.

Review the bot's size and **Min size type**. An amount expressed in tokens is not the same amount expressed in quote currency.

## Order below exchange minimum

A small quote can be rejected after quantity rounding. Use the exchange's stated minimum and increments, then compare **Min order size**, its unit and the final rounded amount.

## Only one side has an order

Read **Mode** first: **Bid only** and **Ask only** intentionally restrict a side. If **All** is selected, look at available funds, the reference and the recorded rejection for the missing side.

## Spread looks twice as wide as expected

**Max spread** is measured per side. Do not read it as the complete distance from bid to ask. Compare each quote with its reference before diagnosing an incorrect spread.

## Rates problem or no new quotes

An unavailable or invalid source can block quoting. Read the account's source and the current error; reopening the drawer does not refresh a failed external feed.

If Depth Support is also involved, its spread condition can prevent support orders even while the MM ladder remains visible.

[Spread settings](https://docs.ansio.trade/spot/other-bots.md) · [Price sources](https://docs.ansio.trade/spot/price-source.md) · [Alert timing](https://docs.ansio.trade/alerts/rules.md)


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