TradingView Alerts Not Working? 9 Causes and Fixes
Alerts that never fire, fire late, or fire twice almost always come down to nine settings. Work through them in order and you'll find the one causing your problem.
TradingView Alerts Not Working? 9 Causes and Fixes
An alert that doesn't arrive is worse than no alert at all, because you stopped watching the chart on the assumption it would. Here are the causes, ordered from most to least common.
1. The alert expired
Alerts on lower TradingView plans expire after a set period, and any alert can be set to "Only Once" — which deletes itself after firing. Open the alerts panel on the right-hand side and check the status column. Greyed-out alerts have stopped.
Fix: set the trigger to Once Per Bar Close and, where your plan allows, set expiry to open-ended.
2. It's waiting for the bar to close
"Once Per Bar Close" means exactly that. On a 4-hour chart, a condition met three minutes into the candle will not notify you for another three hours and fifty-seven minutes. This is a feature, not a fault — closing-bar alerts are the ones that don't fake you out.
Fix: if you want earlier warning, run a second alert on a lower timeframe rather than switching to intrabar triggers on the high one.
3. Notifications are switched off somewhere
There are four separate places notifications can be muted:
Fix: work down that list in order. The phone-level ones are the usual culprit because they're set once and forgotten.
4. You're signed into a different account on mobile
Push notifications go to the account that created the alert. If your phone is signed into a second account, nothing arrives.
5. The alert condition can never actually happen
Alerts built on a crossing of two values that never cross, or a price level already passed in the wrong direction, sit silent forever. TradingView will happily create an alert that is logically impossible to trigger.
Fix: open bar replay, wind back a few weeks and confirm the condition has occurred historically. If it never happened, the logic is wrong.
6. The indicator repaints
If the script recalculates history, the alert condition it reports now may not be the condition it reported live. You get alerts that appear to fire at points the chart no longer shows, or none at all.
Fix: verify the script with bar replay first. See our guide on repainting indicators.
7. You hit the alert limit
Every plan has a maximum number of active alerts. New ones silently fail to save, or older ones get pushed out.
Fix: delete stale alerts. Keeping fewer, higher-quality alerts beats a hundred you ignore.
8. Webhook alerts are being rejected
For webhook alerts, the receiving endpoint must accept a POST over HTTPS on port 80 or 443 and respond quickly. A slow, self-signed or redirecting endpoint will fail.
Fix: log the incoming request at your endpoint to confirm it's being hit at all. If nothing arrives, the problem is the URL. If it arrives and nothing happens, the problem is your parser.
9. The chart's symbol or timeframe changed
Alerts are bound to the symbol and timeframe of the chart they were created on. Editing the chart afterwards doesn't move them.
Fix: check the alert's description line — it states the symbol and interval it's watching.
A quick diagnostic order
Is the alert still active? → Has the bar closed? → Are notifications enabled at all four levels? → Could the condition ever be true? → Does the script repaint?
Nine times out of ten you'll find it in the first three.
FAQ
Why do TradingView alerts fire twice?
You likely have two alerts on the same condition, or a trigger set to Once Per Bar on a chart where the condition stays true across several bars.
Do alerts work when TradingView is closed?
Yes. Alerts run on TradingView's servers, so email and push notifications arrive with the browser closed. Only popup and sound alerts require an open tab.
How late are TradingView alerts?
Server-side alerts usually arrive within seconds of the trigger. Longer delays are nearly always delivery-side — email filtering or phone battery saving.
Can I get alerts from an invite-only script?
Yes, as long as the script exposes alert conditions and access has been granted to your username.
Alerts that fire on closed candles
SimpleAlgo's alerts are built on confirmed, closed-candle conditions, so what you're notified about is what stays on the chart. Setup takes a couple of minutes once your TradingView username is connected — from $5.77/week on the annual plan, with a 7-day money-back guarantee. See what you get.
Filed under

Written by
Nikolas MetreveliFounder of SimpleAlgo
Nikolas wrote his first real code at 12 and freelanced software tools and websites for small businesses before finding the markets at 15. He builds and maintains every SimpleAlgo indicator and writes these guides from hands-on use of the tools.
More about Nikolas and SimpleAlgoRelated Articles
How to Set Up TradingView Alerts That Actually Fire
Price alerts, indicator alerts, and alert conditions explained — plus the settings that stop your alerts firing late, twice, or not at all.
How to Automate TradingView Indicators with Alerts and Webhooks
Turn indicator conditions into automated actions using TradingView alerts and webhooks — what is possible, what is not, and the safe way to set it up.
TradingView Alerts Arriving Late? Why, and How to Fix It
An alert that lands three minutes after the move is worse than no alert. Here's what causes the lag and which part of it you can actually control.
Related tools and guides
Next steps on this topic from the rest of the SimpleAlgo library.