Skip to content
Launch app
Browse documentation

Missing history

Check confirmation and data availability when activity is missing.

Reviewed .

The short version#

Positions and balances are read straight from the chain and are always available while the chain is. History — activity lists, market charts and the realised profit-and-loss figure — comes from an optional indexing service, and when that service cannot vouch for a complete record the venue says so rather than drawing a partial one.

What you will see#

  • On a profile: "Complete history is unavailable. P/L is not estimated." and an empty chart.
  • On a market: the chart shows what direct chain reads allow and says when history is unavailable.
  • On combos: "Combo history is catching up or unavailable."

None of these means your positions are gone. They are on chain and on the positions tab.

Why it happens#

The history service is refused, and its data discarded, whenever any of these is true:

  • it is not configured for the build — it is optional, and off by default;
  • it reports itself incomplete — a backfill is still running, or a gap is recorded;
  • it is indexing a different chain or a different contract than the one this build uses — a local chain that was reset with the same id is a different chain, and the service will not mix the two;
  • its revision changed mid-read — the record was rebuilt while the page was reading it, so the page starts over rather than stitching two versions together;
  • it did not answer within ten seconds.

A missing index is reported as unavailable, never as an empty successful list, because an empty list would read as "you have never traded".

What is not estimated#

The venue does not compute a profit-and-loss figure from partial history, does not mark open positions to a pool share, and does not fill a chart gap with an interpolated line. See P&L scope.

What to do#

Nothing is required of you. When the service catches up, open pages are told through a small update stream and re-fetch; otherwise reloading the page later is enough. If the build you are using has no history service at all, the activity and performance screens will stay in this state, and the positions tab remains the record.