> For the complete documentation index, see [llms.txt](https://docs.ensemble.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ensemble.io/data-and-transparency/status-and-data-quality.md).

# Status and data quality

Distinguish fresh observations from limited, stale, or unavailable data.

Missing data is not a zero balance. A useful status tells you whether the vault is restricted or the system simply cannot read it right now.

## Status vocabulary

A paused vault blocks an action through contract policy. An unavailable reading leaves the value unknown. Check which condition applies before deciding whether to wait or retry.

| State       | Meaning                                                                                   |
| ----------- | ----------------------------------------------------------------------------------------- |
| Available   | Required reads succeeded and are fresh; a transaction still needs capacity and simulation |
| Limited     | Operation is possible only within current capacity or coverage                            |
| Paused      | A contract route or vault control blocks the action                                       |
| Emergency   | The vault is following emergency-state behavior                                           |
| Stale       | Last successful observation exceeds its freshness policy                                  |
| Unavailable | A required read failed or compatibility is unknown                                        |

## Freshness

Check the observation block and time before relying on a balance or estimate. A page loading successfully does not establish that its values are current. Refresh the selected vault before preparing a transaction; an earlier reading cannot reserve capacity.

## Coverage

A report may include only part of the requested period or only some trades.

Check the requested and returned time ranges, observation count, and whether results were truncated. Execution-cost totals may be incomplete when some trades lack attribution.

## Distinguish zero from an unreadable limit

A successful capacity read can return zero because cash, route usage or vault state prevents an exit. A compatibility error or failed Core input is different: the amount is unknown. Preserve that distinction instead of interpreting both as a worthless position.

Read [Share accounting](/how-it-works/nav-and-share-accounting.md), then check [transaction troubleshooting](/use-ensemble/transaction-troubleshooting.md) for a zero-capacity result. A fresh simulation still needs to pass before submission.