Why is my TradingView alert not triggering?

What this means in practice

Check the server-side alert instance, not only the current chart. Alerts use a saved snapshot; repainting, expiration, runtime errors and frequency limits can also explain missing alerts. This page is specifically about “Why is my TradingView alert not triggering?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Old snapshot

Inspect the mechanism named by “Scenario A — Old snapshot” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Old snapshot on question 11, use that evidence specifically to answer “Why is my TradingView alert not triggering?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Intrabar signal vanished

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 B — Intrabar signal vanished on question 11, use that evidence specifically to answer “Why is my TradingView alert not triggering?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Expired alert

Inspect the mechanism named by “Scenario C — Expired alert” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Expired alert on question 11, use that evidence specifically to answer “Why is my TradingView alert not triggering?”; keep it separate from the evidence for the other scenarios on this page.

Scenario D — Runtime error

Inspect the mechanism named by “Scenario D — Runtime error” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario D — Runtime error on question 11, use that evidence specifically to answer “Why is my TradingView alert not triggering?”; keep it separate from the evidence for the other scenarios on this page.

Scenario E — 15-in-3-min limit

Inspect the mechanism named by “Scenario E — 15-in-3-min limit” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario E — 15-in-3-min limit on question 11, use that evidence specifically to answer “Why is my TradingView alert not triggering?”; 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 is my TradingView alert not triggering?”, 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.