NRUNO Trading Automation Wiki · Question 55

Can a repainting TradingView strategy still be automated safely?

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

Sometimes, but only if the realtime behavior is intentional, documented and tested. A repainting script can be valid for live use while still making historical charts or backtests unsuitable evidence of what happened in realtime.

What this means in practice

Sometimes, but only if the realtime behavior is intentional, documented and tested. A repainting script can be valid for live use while still making historical charts or backtests unsuitable evidence of what happened in realtime. This page is specifically about “Can a repainting TradingView strategy still be automated safely?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Intentional intrabar scalper

Inspect the TradingView alert log during the still-open candle. Realtime recalculation can make the condition true several times; add explicit intrabar state or a per-bar guard if the strategy intends only one logical action. For Scenario A — Intentional intrabar scalper on question 55, use that evidence specifically to answer “Can a repainting TradingView strategy still be automated safely?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Unintentional HTF repaint

Inspect the mechanism named by “Scenario B — Unintentional 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 — Unintentional HTF repaint on question 55, use that evidence specifically to answer “Can a repainting TradingView strategy still be automated safely?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Backtest looks better after reload

Inspect the mechanism named by “Scenario C — Backtest looks better after reload” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Backtest looks better after reload on question 55, use that evidence specifically to answer “Can a repainting TradingView strategy still be automated safely?”; 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 “Can a repainting TradingView strategy still be automated safely?”, 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: Sometimes, but only if the realtime behavior is intentional, documented and tested. A repainting script can be valid for live use while still making historical charts or backtests unsuitable evidence of what happened in realtime.

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.