TradingView Alerts Arriving Late? Why, and How to Fix It

There are two different problems hiding behind "my alert was late", and they have completely different fixes. Work out which one you have first.

Problem A: the alert fired on time, you saw it late

The alert log shows it triggered at the right moment, but the notification reached you minutes afterwards. That's a delivery problem, not an alert problem.

Check the delivery channels you enabled. Email is the slowest route by a wide margin and can queue for minutes. App push is much faster. Browser popups are instant but only while the tab is open.

Check your device. Battery saver modes, background app restrictions and Do Not Disturb all hold push notifications. On both iOS and Android, the platform app needs notification permission and background activity allowed, and on Android it should be excluded from battery optimisation.

Check the browser tab. Background tabs get throttled aggressively. If you rely on browser alerts, keep the chart in a visible window or use push instead.

Problem B: the alert fired later than the condition

The condition happened at 14:31 and the alert timestamp says 14:34. This is almost always the trigger setting.

"Once per bar close" waits for the candle to finish. On a 15-minute chart, a condition met one minute into the candle fires 14 minutes later. That's the setting working correctly — it's the whole point of close confirmation.

If you need immediacy, switch the trigger to "Once per bar". Understand the trade-off: intrabar triggers fire on conditions that can disappear before the candle closes, which produces alerts on moves that never actually completed.

Other causes worth checking

Data feed delay. If you don't have a real-time subscription for the exchange, your chart is showing delayed data and every alert inherits that delay. The delay indicator appears near the symbol name.

Server-side evaluation. Alerts are evaluated on TradingView's servers, which is why they work with the browser closed. Under heavy market-wide load there can be small delays. Nothing you configure changes this.

Overly complex conditions. Scripts that reference multiple higher timeframes have to wait for those timeframes to update. A condition depending on a 4-hour value can't confirm faster than the 4-hour chart does.

Alert recreated on a different timeframe. A condition set on the chart's timeframe behaves differently on the 1-hour than the 5-minute. Check which chart the alert was created from.

A practical setup

If nothing fires at all

That's a different guide — alerts not working covers expired alerts, exhausted alert slots and conditions that can never be true.

Frequently Asked Questions

Are TradingView alerts real time?

Alerts are evaluated on TradingView's servers as data arrives, but an alert set to trigger once per bar close only fires when the bar closes. Delivery through email or push can add a few seconds on top.

How do I make alerts arrive faster?

Use push notifications or webhooks instead of email, and pick the trigger condition that matches when you actually want to know: once per bar for intrabar moves, once per bar close for confirmed signals.

SimpleAlgo is not affiliated with, endorsed by, or sponsored by TradingView. TradingView is a trademark of TradingView, Inc. Platform menus and settings change over time — if a step doesn't match what you see, check TradingView's current help documentation.