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

# Handle stale data and exchange errors

> Distinguish a stale reading from a zero balance or position, investigate an exchange error and avoid repeating an action while its result is still unknown.

ANSIO displays exchange state and action results separately. A delayed reading does not prove that an order failed, and an accepted request does not prove that it executed.

![A failed source showing No quote and the selected reference market.](https://mintcdn.com/ansio/TbUlSsAFRzZei_af/images/docs/source.jpg?fit=max\&auto=format\&n=TbUlSsAFRzZei_af\&q=85\&s=295faed7000a1b6245895cacd70f550f)

A source failure in the ANSIO demo. The exit record explains whether orders were held or cancelled.

## Is the reading current?

Read the timestamp and connection state next to the value. **Offline (last known)** is an old observation, not a fresh confirmation.

Missing balances, positions or prices should not be treated as zero. A gap in a historical chart also does not mean trading stopped throughout that gap.

A view refresh asks for current information. It is different from restarting a strategy.

## Read the exchange response

Use the exact error in the account's activity or bot status. Common categories include:

| Category | What to inspect |
| - | - |
| Authentication or permission | Whether the key is valid and has the required account and trading permissions. |
| Market restrictions | Pair, contract, precision, minimum size and supported account mode. |
| Insufficient funds or margin | Available balance, existing exposure and strategy allocation. |
| Reference unavailable | Source selection and its latest update. |
| Connection or rate-limit response | The latest result and timestamp before another request. |

Do not post a secret key or passphrase when sharing the error.

## When an action has an uncertain result

If Start, Stop, Restart or Close has been accepted but the result is unclear, first read the latest bot, order and position state. Repeating the action immediately can make the sequence harder to understand.

The [Futures close flow](https://docs.ansio.trade/futures/flatten.md) refuses to submit without a fresh position. Keep that requirement intact rather than substituting a remembered size.

## After the connection returns

Confirm that balances and positions have a new timestamp. Then review bot status, resting orders and any pending Autopilot tasks. Reconnecting the view does not automatically resume a paused task.

For persistent errors, send [Support](https://docs.ansio.trade/support.md) the exact response, affected account, action and time.


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