Bar-close vs intrabar alerts in TradingView: when each one misleads you
TradingView lets you set alerts to trigger once per bar close, once per bar, or every time the condition is met. The difference matters more than people think.
Intrabar alerts fire as soon as the condition is true during the bar. That's fast, but on a candle that's still forming, the condition can come true and then become false again before the bar closes. If your alert is for price crossing above a moving average, an intrabar alert might fire on a spike that reverses within seconds. You get notified about a cross that never happened on the closed chart.
Bar-close alerts only fire when the bar closes with the condition true. That matches what you see on historical charts, which is what most strategies are built on. The cost is a delay of up to one full bar. On M1 that's a minute, on M15 it's up to fifteen minutes.
For indicator based conditions, intrabar alerts can also be affected by repainting. An indicator that recalculates on each tick might trigger an alert and then show no signal on the closed bar.
My rule is to match the alert to how the strategy was designed. If the strategy uses closes, use bar-close alerts. If it relies on touches of a level, intrabar can make sense.
Bar-close vs intrabar alerts in TradingView: when each one misleads you
Re: Bar-close vs intrabar alerts in TradingView: when each one misleads you
If you use a higher timeframe condition on a lower timeframe chart, using functions that look at another timeframe's data, the alert can behave differently than you expect. An alert based on H1 data on an M5 chart might fire on M5 bar close while the H1 bar is still forming. If the H1 condition later changes before its own close, the alert fired on something that didn't hold. It's one of the easier ways to end up with alerts that don't match the historical chart. If you rely on those, check the alert on a few historical examples first and see whether it matches what the closed bars show.
It’s Fairman 
Re: Bar-close vs intrabar alerts in TradingView: when each one misleads you
A practical habit that helps: when you set up a new alert, keep a note of each time it fires for a week and compare it to the chart afterwards. You'll quickly see whether it's firing on conditions that hold, or if a lot of alerts are coming from spikes or repaints. It's tedious, but it's better than finding out after acting on false alerts in live trading. I'd also check the alert's expiry date, since TradingView alerts can stop working without much notice. A quick weekly look at the alert list stops that from catching you out.
It’s Fairman 
Re: Bar-close vs intrabar alerts in TradingView: when each one misleads you
Repainting is related to this. Some indicators recalculate past values when new data arrives, so the alert fires based on a value that later changes. Then when you look at the chart, the signal isn't where the alert said it was. Checking whether an indicator repaints, by watching it live on a lower timeframe for a while, avoids building alerts on something that won't match the chart afterwards. TradingView's replay mode helps here too, though it doesn't always show repainting the way live data does. Watching live for a few days is still the most reliable check.
It’s Fairman 
-
FXS Prop Desk
- Posts: 1689
- Joined: Wed Oct 07, 2026 9:52 am
Re: Bar-close vs intrabar alerts in TradingView: when each one misleads you
Intrabar alerts on a candle still forming are a common source of false signals. The condition can be true for a few seconds and then disappear by the close, but the alert has already been sent.
Once per bar close is safer for most strategies. For faster strategies, using a lower timeframe for the alert and checking the condition on the higher timeframe manually can give a good balance between speed and reliability.
Once per bar close is safer for most strategies. For faster strategies, using a lower timeframe for the alert and checking the condition on the higher timeframe manually can give a good balance between speed and reliability.
FXS Official Team | The Idea Lab & Strategy
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Bar-close vs intrabar alerts in TradingView: when each one misleads you
It sounds like pure discipline. An indicator can flash and vanish while a bar is forming, so acting only on the closed bar removes the noise. That part is true. The myth is the idea that it comes free.
Take a scalp built on a break of a 5 minute high. Waiting for the close means the entry happens at the open of the next bar, often several pips beyond the level that triggered the idea. The stop distance, measured from a sensible invalidation point, has grown, while the target did not. The reward to risk ratio the setup had on paper quietly shrinks. On fast moves the move can be mostly done by the time confirmation arrives.
Acting intrabar has the opposite problem. It gets the better price, but many signals will reverse before the bar finishes. A close above a level and a spike above a level that closes back inside are very different events, and trading the spike means paying the spread on a lot of fakeouts.
Neither approach wins in general. What changes the answer is how the strategy's edge is distributed: whether most of the profit sits in the first few pips of a move or in the continuation. That is measurable. Test both on the same data and compare average entry slippage against the level, plus the fakeout rate.
Some people settle on a hybrid, such as entering intrabar only after price has held beyond the level for a set number of seconds, which filters the quickest spikes without waiting for the full bar.
What does your data show on the cost of waiting versus the cost of fakeouts for your setup?
Take a scalp built on a break of a 5 minute high. Waiting for the close means the entry happens at the open of the next bar, often several pips beyond the level that triggered the idea. The stop distance, measured from a sensible invalidation point, has grown, while the target did not. The reward to risk ratio the setup had on paper quietly shrinks. On fast moves the move can be mostly done by the time confirmation arrives.
Acting intrabar has the opposite problem. It gets the better price, but many signals will reverse before the bar finishes. A close above a level and a spike above a level that closes back inside are very different events, and trading the spike means paying the spread on a lot of fakeouts.
Neither approach wins in general. What changes the answer is how the strategy's edge is distributed: whether most of the profit sits in the first few pips of a move or in the continuation. That is measurable. Test both on the same data and compare average entry slippage against the level, plus the fakeout rate.
Some people settle on a hybrid, such as entering intrabar only after price has held beyond the level for a set number of seconds, which filters the quickest spikes without waiting for the full bar.
What does your data show on the cost of waiting versus the cost of fakeouts for your setup?
Re: Bar-close vs intrabar alerts in TradingView: when each one misleads you
Something to consider is how alerts behave during quiet times. An intrabar alert on M1 might fire repeatedly if price keeps crossing a level back and forth. TradingView has options like 'once per bar' or 'once per bar close' to control this. If you get flooded with alerts on a level, changing the frequency setting usually solves it without changing the condition itself. Does anyone use webhook alerts into an EA, and how do you handle duplicates? Webhooks need a bit of extra handling, since the same alert can sometimes be delivered twice. Giving each alert a unique ID and having the receiving code ignore repeats is a simple fix.
It’s Fairman 