NRUNO Trading Automation Wiki · Question 77

Why did my TradingView alert fire at a different price than the chart marker?

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

Chart markers, alert evaluation and live broker execution can reference different moments and prices. Realtime updates, strategy fill timing, bid/ask spread, latency and slippage can all create a legitimate difference.

What this means in practice

Chart markers, alert evaluation and live broker execution can reference different moments and prices. Realtime updates, strategy fill timing, bid/ask spread, latency and slippage can all create a legitimate difference. This page is specifically about “Why did my TradingView alert fire at a different price than the chart marker?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Intrabar alert

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 — Intrabar alert on question 77, use that evidence specifically to answer “Why did my TradingView alert fire at a different price than the chart marker?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Strategy fill marker

Inspect the mechanism named by “Scenario B — Strategy fill marker” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Strategy fill marker on question 77, use that evidence specifically to answer “Why did my TradingView alert fire at a different price than the chart marker?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Bid/ask execution

Inspect the mechanism named by “Scenario C — Bid/ask execution” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Bid/ask execution on question 77, use that evidence specifically to answer “Why did my TradingView alert fire at a different price than the chart marker?”; 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 did my TradingView alert fire at a different price than the chart marker?”, 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: Chart markers, alert evaluation and live broker execution can reference different moments and prices. Realtime updates, strategy fill timing, bid/ask spread, latency and slippage can all create a legitimate difference.

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.