Choose a past date or valuation minute

Select a valuation, not merely a calendar label

Options tools with Date and the one-minute slider can evaluate eligible inputs at a historical point. The selected trading date and session determine the available window; the slider chooses a valuation minute within that context. This is different from changing a chart's visual interval. A five-minute chart can still be evaluated from a particular eligible historical cutoff.

Choose the selection in order

Set the market context before moving the slider so the available range is meaningful.

1. Choose the underlying or exact source family.
2. Select RTH, GTH or Combined as supported.
3. Choose an available trading date.
4. Read timeline/history availability before choosing a minute.
5. Move the slider to the desired eligible valuation.
6. Match that date/minute in related tools for comparison.
7. Return to the current/live selection explicitly when you finish the historical investigation.

Input cutoffs control what is knowable

A historical model needs dated chain, quotes, reference prices and source/model availability timestamps. It cannot reuse a newer chain simply because that is what the server has now. The same minute can produce data for one metric and unavailable output for another when their required inputs differ. A history-building state describes preparation, while a partial state describes actual incomplete coverage. Neither should be interpreted as a model value of zero.

Worked example: compare a level at two minutes

Choose one date/session and record a Key Levels value at an eligible early minute. Move later while keeping model, expiry and unit settings fixed. A change can reflect later eligible observations or valuation time. Return early and confirm the old cutoff does not show future chart points. If a repair changes the earlier value afterward, inspect correction/coverage status rather than assuming the slider is meant to preserve every obsolete arrival-time estimate.

Troubleshoot unavailable slider positions

Check whether the requested point is inside the selected session and retained/history bounds. Narrow the range or choose a coarser sampling request when the specific feature reports capacity limits. Wait for explicit preparation progress rather than repeatedly changing settings. If several widgets differ, verify linkage and individual date chips. Send support the selected minute, observed source bounds and history message, not only the day displayed in the page header.

Requested range and observed coverage are separate

A requested start/end window describes what you asked for. Observed bounds, gaps and completeness describe which eligible retained inputs actually exist. Retained futures executions, BBO and captured depth cover the current and previous futures session; standard option, chain and reference events have seven-day retention. Individual tools can impose narrower query, event, row, byte or preparation limits. Selecting a wider window does not cause every missing exchange observation to be downloaded automatically.

A running feed or a successful current snapshot proves neither an earlier session prefix nor continuous historical depth. Corrections are resolved before time filters, so a corrected timestamp can move an event into or out of a selected range. Incomplete capture must stay partial even if the visible line looks continuous at the chosen scale. Inspect source and coverage metadata before relying on totals. When asking for help, provide requested bounds, observed bounds, the exact dated instrument and the gap or limit message rather than only the page's selected date.

Use an explicit comparison table in your notes

For each historical checkpoint, record symbol/root, trading date, session, selected minute, metric, unit, model and expiry scope. Then record the actual observed/source time and quality state. This separates the user's requested valuation from the inputs the tool could supply. A screenshot with only the Date chip omits most of that contract. Two widgets can both show the same day while one is still live, one is pinned to a minute and another is waiting for history.

An appropriate small experiment changes one minute at a time while leaving other selectors fixed, then compares a named hovered point or total. Changing Period is a separate aggregation experiment; it should not be used to imply more precise source availability. If a later repair changes an earlier checkpoint, document the new coverage and correction context instead of treating the original screenshot as an immutable truth. The history tools aim to use eligible canonical evidence, while an old browser image can preserve a provisional display that has since been corrected.