# Repainting, bar confirmation, and higher-timeframe timing

Distinguish changing live candles, delayed pivot drawings, and historical lookahead, with a practical Core verification procedure.

Canonical: https://getphantomflow.com/docs/repainting-and-confirmation
Updated: 2026-09-09
Author: Phantom Flow documentation

A historical chart does not always show what a person could have seen at the time. To evaluate Core fairly, separate three timing questions: whether the current candle was closed, when a pivot was recognized, and whether higher-timeframe data was available yet.

## The open candle can change

During a live candle, the current price, high, and low can change. Conditions based on those values can appear and disappear before closing. Waiting for the chart bar to close reduces this particular source of disagreement. It does not prove that every drawing or data request is free from other timing effects.

TradingView describes these differences in its [repainting documentation](https://www.tradingview.com/pine-script-docs/concepts/repainting/). Repainting is a category of behavior to investigate, not a single setting with one universal fix.

Core's inputs do not include Pro's Confirmed Bars Only control. Also, choosing Close for order block mitigation selects a price source; it does not make that source stop changing while the candle is open.

## A pivot's location is not its detection time

A turning point needs later price information before it can be recognized. A drawing may then be placed at the earlier turning point or between it and a later break. This can make a historical chart appear more timely than the information actually was.

When journaling a structure event, record when it became visible or triggered an alert. Do not use the horizontal position of its label as the assumed decision time.

## Higher-timeframe confirmation is separate

Suppose a five-minute chart displays information from an hourly candle. Closing a five-minute bar does not close the hour. The requested values may still change during the rest of that hourly candle.

There is an additional caveat in the Core FVG source reviewed for these docs: its higher-timeframe request includes current higher-timeframe high/low values with lookahead behavior. Historical gap drawings can therefore expose information earlier than it was available live. We do not describe Core MTF gap history as a verified non-repainting record.

TradingView's [timeframe request documentation](https://www.tradingview.com/pine-script-docs/concepts/other-timeframes-and-data/) explains why requested data timing and lookahead must be assessed together. A chart-bar-close alert does not repair historical lookahead.

## A practical observation check

1. Record the script version, full symbol, chart type, session, timeframe, inputs, and any requested interval.
2. Capture the first live appearance of the event with a timestamp.
3. Capture it again after the chart candle closes.
4. For MTF information, capture it after the requested candle closes too.
5. Reload and compare the same timestamps and prices.

Write down what changed and when. Keep absent or disappearing events in the record. If the first available live time cannot be established, label the historical observation timing-unverified.

This procedure checks observed behavior for that version and context. It cannot certify every market or input combination. Use the [evaluation journal](/docs/evaluate-an-indicator) to preserve the evidence and send a concrete discrepancy through [support](/support).

## Related articles

- [Fair value gaps: identify the range and its limits](https://getphantomflow.com/docs/fair-value-gaps)
- [Create and troubleshoot Phantom Flow Core alerts](https://getphantomflow.com/docs/core-alerts)
- [Evaluate an indicator with a reproducible journal](https://getphantomflow.com/docs/evaluate-an-indicator)

Educational documentation. Phantom Flow visualizes chart information and provides alerts. It does not execute trades or guarantee results.