New

11 tools. $557.98 if bought one by one. 5 new Premium desks inside.$557.98 one by one

$97 once$97See all 11See it
ProEA Lab · MT5, TradingView and trading research · Evidence standards
Indicators

TradingView Alert Not Triggering? Five Causes, One at a Time

Most TradingView alerts that 'don't work' are doing what their settings say: firing once and stopping, waiting for the bar to close, running the old version of your script, or expired. How to tell which, and the fix for each.

PL · 4 min read
Explainer cover titled TradingView alert not triggering: check the frequency. Two simulated 5-minute candles against a dashed level at 2,400.00: the first pokes above and closes back below, the second closes above, with bells marking where Once per bar fires, inside both bars, and an alert log listing the two firings.
A TradingView alert that won't fire is usually doing what its settings say. Check five things: the frequency (Only once stops after one firing, Once per bar close waits for the close), whether you changed the script or its inputs after creating the alert (it keeps the old copy), whether it expired (two months at most on standard alerts), whether your plan's limit is full, and whether the condition was met on a live bar.
Same alert, same bars, three frequencies.One bar pokes above the level and falls back; the next one holds. Pick a frequency.
2396.002397.002398.002399.002400.002401.002400.0009:4009:4509:10firedfiredAlert: crossing 2400.00 · Once per barALERT LOG09:40 bar · mid-bar · price 2400.4009:45 bar · mid-bar · price 2400.20Once per bar: it fires inside both bars, first on the 09:40 bar's poke above2400.00, a cross the closed bar no longer shows, then on the 09:45 bar.

Simulated 5-minute candles and an illustrative level, not market data.

Read as text
  1. The alert: price crosses above 2400.00, set to "Once per bar". Six bars closed below it.
  2. The 09:40 bar trades up to 2400.90 and closes at 2398.80, back below. The 09:45 bar crosses again and closes at 2401.40.
  3. Once per bar: it fires inside both bars, first on the 09:40 bar's poke above 2400.00, a cross the closed bar no longer shows, then on the 09:45 bar.

How this window was chosen: Only once fires the first time the condition is met; Once per bar fires at most once per bar, as soon as it is met; Once per bar close needs the bar to close with it met. Alerts only trigger on the live bar. From TradingView's alert frequency help and the Pine Script alerts page, checked 2026-10-08.

1. The frequency

TradingView's alert frequency help, checked 2026-10-08:

FrequencyFiresWatch for
Only onceThe first time the condition is metThen it stops; the next signal gets nothing
Once per barAt most once per bar, as soon as it's metMid-bar signals that vanish by the close
Once per bar closeOnly when the bar closes with it metUp to one bar later than the cross

Pine's alerts page says the same for script alerts and recommends Once per bar close to avoid alerts on values that change before the close.

2. You edited the script after creating the alert

"TradingView saves a mirror image of the script and its inputs" when you create an alert, so later changes to the script or its inputs don't reach it (Pine alerts, checked 2026-10-08). Delete the alert and create it again after every change. This catches people who add a script from source, fix it, and keep the old alert.

Use itRecreate the alert every time you save a new version of the script.

Watch outAn alert made yesterday runs yesterday's code.

3. It expired

Alerts have an expiry. A standard alert lasts at most two months; Premium and Ultimate can set alerts that don't expire (TradingView alerts help, checked 2026-10-08).

4. Your plan's limit is full

Active alerts per plan, from the pricing page, checked 2026-10-08:

PlanPrice alertsTechnical alerts
Basic3none listed
Essential2020
Plus100100
Premium400400
Ultimate1,0001,000

5. The condition was never met on a live bar

Alerts only trigger on the live bar (Pine alerts). A signal you see on historical bars, or one that repaints, may never have been true in real time.

An alert that fired once and stopped, or never fired on yesterday's bars, is working as set.

Use this animation on your site.

Frequently asked questions

Why is my TradingView alert not triggering?

Check five things in order: the frequency (Only once stops after the first firing; Once per bar close waits for the close), whether you edited the script or its inputs after creating the alert, whether the alert expired, whether your plan's alert limit is full, and whether the condition was met on a live bar at all.

What is the difference between Once per bar and Once per bar close?

Once per bar fires the first time the condition is met in a bar, even mid-bar. Once per bar close fires only if the condition is still met when the bar closes. The first is faster; the second won't fire on a cross that disappears before the close.

I changed my indicator's settings. Why does the alert still use the old ones?

TradingView saves a copy of the script and its inputs when you create the alert. Later changes don't reach it, per the Pine Script alerts page. Delete the alert and create it again.

Why did my alert fire but the chart shows no signal?

It fired mid-bar on a value that changed before the bar closed. Use Once per bar close if you only want signals the closed chart will still show.

How many alerts can I have on TradingView?

On the pricing page, checked 2026-10-08, active price alerts are 3 on Basic, 20 on Essential, 100 on Plus, 400 on Premium and 1,000 on Ultimate, with the same numbers for technical alerts on the paid plans.

Do TradingView alerts expire?

Yes. TradingView's help says a standard alert can last at most two months; Premium and Ultimate can set alerts with no expiry.

Continue reading

How to Open a .pine File (and Get It onto TradingView)

A .pine file is plain text: Pine Script source code with a .pine name. Any text editor opens it, and TradingView takes it by copy and paste into the Pine Editor. Open yours below for limited version, declaration and paste checks; compile it in Pine Editor.

Oct 8 · ProEA Lab

Explainer cover titled How to open a .pine file: it's plain text. A file card named session-range.pine opened into its reading: Pine version v6, type indicator, title Session range (example), 15 lines, a warning that Markdown fence lines were removed, and the five-step route into TradingView from Open the file to Add to chart.

Pine Script to MQL5: Converting a TradingView Strategy to an MT5 EA

How to turn a TradingView indicator or strategy into an MT5 indicator or EA: where Pine and MQL5 run differently, which calls map to which, the time-zone trap, a worked port of one rule from our Opening Range Desk, and how to check the port bar by bar.

Oct 8 · ProEA Lab

Explainer cover titled Pine Script to MQL5: same rule, two clocks. Two stacked 5-minute charts of the same simulated candles. On the top pane, TradingView Pine in New York time, an orange box marks the 09:30–09:45 opening range and a Short signal follows two closes below it. On the bottom pane, MT5 in server time with a fixed offset of minus 7 hours in a week the server is 6 hours ahead, the box lands an hour late on the 10:30 candles and the signal is Long.

How Many Indicators Can You Add on TradingView? Every Plan

TradingView caps indicators per chart by plan: 2 on Basic, 5 on Essential, 10 on Plus, 25 on Premium and 50 on Ultimate, read from its pricing page on 2026-10-08. What the cap counts, and the one way past it that doesn't cost a plan: put several indicators in one Pine script.

Oct 8 · ProEA Lab

Explainer cover titled TradingView indicator limit: 2, 5, 10, 25 or 50. A sketch chart above a row of five indicator slots on the Essential plan: the first slot holds one Pine script with three indicators in it, then MACD, VWAP and Bollinger Bands, and one slot left free.