NRUNO Trading Automation Wiki · Question 78

Why does my TradingView strategy behave differently after the chart reloads?

Pine Script & TradingView AlertsLast reviewed: 25 Aug 2026
Short answer

After reload, realtime bars become historical bars and lose their original intrabar update sequence. Tick-sensitive, repainting or realtime-only logic can therefore display different historical behavior.

What this means in practice

After reload, realtime bars become historical bars and lose their original intrabar update sequence. Tick-sensitive, repainting or realtime-only logic can therefore display different historical behavior. This page is specifically about “Why does my TradingView strategy behave differently after the chart reloads?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Realtime tick logic

Validate protection in the symbol's real units: direction, price-versus-distance convention, tick size/digits and current minimum distance. Record the normalized value actually sent to cTrader. For Scenario A — Realtime tick logic on question 78, use that evidence specifically to answer “Why does my TradingView strategy behave differently after the chart reloads?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — HTF repaint

Inspect the mechanism named by “Scenario B — HTF repaint” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — HTF repaint on question 78, use that evidence specifically to answer “Why does my TradingView strategy behave differently after the chart reloads?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Reload

Inspect the mechanism named by “Scenario C — Reload” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Reload on question 78, use that evidence specifically to answer “Why does my TradingView strategy behave differently after the chart reloads?”; keep it separate from the evidence for the other scenarios on this page.

What to check

  • active server-side TradingView alert instance
  • saved symbol, timeframe and inputs
  • realtime versus confirmed-bar behavior
  • exact message emitted by the active alert

Practical rule

For “Why does my TradingView strategy behave differently after the chart reloads?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.

Decision summary

Direct answer: After reload, realtime bars become historical bars and lose their original intrabar update sequence. Tick-sensitive, repainting or realtime-only logic can therefore display different historical behavior.

Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.

Primary sources

Need a TradingView → cTrader execution route?

NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.