Read live, partial and unavailable data states

Separate receipt time from observation time

A response can arrive now while containing a market observation recorded earlier. Live transport describes how updates are being delivered; source time describes when the market input was observed. A current socket connection therefore does not establish that every value on the screen is fresh or that the full session was captured. Read the instrument, trading date and source timestamp alongside the connection state. This matters especially during closed markets, when a last-session answer can be the correct available result even though the application itself remains connected.

Interpret partial coverage literally

Partial means the view has admitted useful observations without establishing complete coverage for the requested scope. The chart can still support a bounded observation, such as showing executions that were actually captured, but its totals should not be described as every trade in the exchange session. A depth-only interruption can coexist with continuous valid executions. Conversely, a synchronized current book cannot prove the earlier heatmap is complete. Missing chart periods remain absent rather than becoming invented flat candles or zero-volume proof of inactivity.

Recognize pending history and retained frames

A history request can require bounded preparation before the requested bars or depth inputs are ready. Keep the instrument, date and interval stable while inspecting the visible progress or pending state. Changing the selection repeatedly starts different questions and makes the original outcome harder to assess. When updates fail temporarily, the application can retain the last good frame. That preserves context, but the frame keeps its original source meaning; a retained picture should be read as dated evidence until a newer valid capture is accepted.

Distinguish unavailable causes

Unavailable is a result that needs context, not a single universal failure. The instrument or session may be unsupported, the source may lack a required quote, the historical interval may be outside retention, or the account may not have the appropriate dataset access. A calculated indicator can also be unavailable while its base candles remain valid because it needs different inputs. For example, an index candle does not supply executed stock volume, and historical heatmap spans do not prove the exact replenishment evidence needed by possible absorption.

Check the problem at its narrowest scope

Preserve the current selection while you identify which part is missing. This avoids confusing a filter change with source recovery.

1. Read the full visible status and determine whether it applies to the entire tool or only one layer or indicator.
2. Verify the symbol, exact contract, session, date, expiration range and selected minute.
3. Inspect the latest source time and compare it with the period you expected to see.
4. For Order Flow, open Settings to review execution and depth coverage separately.
5. Use Refresh data for a new capture of the same selection, then note whether the status changes.

Use examples to avoid misleading comparisons

Suppose a Footprint contains executions across a window while the heatmap has a blank section. That does not establish a period with no resting liquidity; it may mean depth continuity was unavailable. Suppose an OHLC candle updates while a volume-dependent study remains empty. The candle can be valid even when that asset lacks known volume. Suppose a Gamma chart and a tape total differ. First compare their units and input scopes: modeled exposure and executed premium are different measures, so matching their update times would not make their numbers comparable.

Prepare evidence that support can reproduce

Create a ticket with the page and section, precise instrument, trading date, session, interval or lookback and the exact error or status text. Include a screenshot with the header, axes and affected layer visible. State whether you were following Live, paused or inspecting a pinned historical point. Explain what changed after a same-selection refresh. Avoid describing a successful connection as proof that the provider history is complete. These concrete observations let support investigate source eligibility, retained coverage and display state without guessing which question the original view was answering.