TradingView Alerts Not Firing: Every Cause in Order

The worst thing about a broken alert is that it looks exactly like a quiet market. No error, no email, no red banner. Your strategy just stops taking trades and you find out on Thursday that the last one was Monday.

Most of the time it's one of three things, and two of them fail without telling you anything.

Start with the alert log rather than the alert settings. Open the Alerts panel, click the alert, open its Log tab. If there are no entries, the alert never fired and the problem is on TradingView's side. If there are entries but nothing reached your platform, the alert fired and delivery failed. That single check cuts the list of possible causes in half, and it takes ten seconds.

Causes on TradingView's side, in order

1. You've hit your plan's active alert limit. This is the most common cause and the nastiest, because creating an alert past the cap can appear to succeed. The dialog closes, the alert looks saved, and it never fires. Count your active alerts against your plan: Essential allows 20, Plus 100, Premium 400. Delete dead ones before adding new ones.

2. The alert expired. Alerts on most paid tiers stop after roughly two months. Not deleted, just dormant, sitting in the inactive section of the alert manager where you won't see them unless you look. Check the expiry column. When you create an alert for automation, set the expiry to open-ended rather than accepting the default.

3. The trigger frequency is "Only Once." It fired, once, and switched itself off. Working exactly as designed and almost never what you wanted. For anything running continuously, use Once Per Bar Close, or Once Per Bar if you accept acting on an unconfirmed candle.

4. Your plan doesn't include webhooks at all. Webhooks start at Essential. The free plan cannot send them, and the giveaway is simple: if the alert dialog shows no Webhook URL field, your plan doesn't have it.

5. The script changed underneath the alert. Update the indicator or strategy an alert is built on and the alert can be left pointing at something that no longer exists in the same form. It survives the edit and quietly stops. Any time you republish a script, check the alerts attached to it.

6. The condition never actually became true. Boring, common, and worth ruling out before you blame the plumbing. An alert set to fire on bar close won't fire mid-candle even when price is clearly through your level, and an intrabar condition that reverses before the close may fire and then look wrong. That's timing, not failure.

7. The market was closed. For stocks and forex, alerts are only evaluated while the instrument is trading. An alert set on a Saturday sits there doing nothing until the session opens, which catches people who test on a weekend and conclude the setup is broken.

8. The chart is a synthetic series. Heikin Ashi, Renko and similar transformed charts don't have real bars in the way an alert expects. Conditions on them can lag or skip. Build the alert on a standard candle series and apply the transformation visually if you want it.

Causes on the receiving side

If the log shows the alert fired but nothing happened downstream, the failure is in delivery or in what received it.

The address has to be reachable and secure. TradingView only sends to a public address over a secure connection. A local address on your own machine, or an address on a nonstandard port, will not work. If you've built your own receiver behind a tunnel, tunnels change address on restart, and the alert is still pointing at the old one.

The receiving end has three seconds. If it doesn't answer in that window, TradingView cancels and moves on. Nothing retries a timeout. A slow receiver looks identical to a broken one from where you're sitting.

The message was malformed. If your platform expects structured text and yours has a missing bracket, a smart quote pasted from a document, or a trailing comma, the whole message arrives as plain text and gets rejected. The alert log shows the refusal even when TradingView did its part correctly.

Repeated failures can get the webhook switched off. If an address fails often enough, TradingView may stop attempting it. Fix the receiver first, then rebuild the alert rather than assuming the old one will resume.

It arrived and was refused for a reason. This is the case people can't diagnose, because TradingView reports a successful delivery and the trade still doesn't exist. The alert was accepted, then the platform on the other end declined to act on it: the strategy was paused, the symbol wasn't one the connected account trades, a risk limit was already reached, or the message didn't match what the strategy expected.

Whether you can see that depends entirely on what you're using. Some tools record every refused signal with the reason attached, which turns a mystery into a one-line answer. Others accept quietly and log nothing, and you're left comparing timestamps. It's worth knowing which kind you have before you need to know.

The two-minute test

When you're stuck, stop reading settings and send one.

Create a fresh alert on a condition you can force — a price level a few ticks away — with the same webhook address and the same message as the broken one. Watch whether it fires, and watch what the log says.

If the test alert works, the original was in a bad state and the fix is to rebuild it rather than repair it. If the test alert fails identically, the problem is the address, the message, or the plan, and you've just narrowed it to three things.

The honest limitation

You can't fully monitor this from inside TradingView, because the failure mode that costs the most produces no event at all.

An expired alert doesn't fire, so it writes nothing to a log. A capped alert never activates, so it has no log to write to. In both cases the evidence is an absence, and absences don't trigger notifications. The only reliable defence is a habit rather than a feature: check your active alert count and your expiry dates on a schedule, and treat a quiet week as something to verify rather than something to accept.

Before you go back to the chart

Open the Alerts panel now and check three columns: status, expiry, and how many you have against your plan's limit. That covers the top two causes on this page and takes under a minute.

Then set every automation alert to open-ended expiry and Once Per Bar Close, so the two silent failures can't happen to you again.

If you want the whole path an alert travels, from the condition firing to an order existing at your broker, the end-to-end version is here — including why a delivered webhook proves less than people assume.

Vectorhelm records every signal it receives, including the ones it refuses and why, so a missing trade is a line you can read rather than a timestamp you have to reconstruct. Alerts in, risk enforced, orders out across MT5 and crypto. It isn't open yet. Early access is here if you want it when it is.

Vectorhelm is execution software. It runs the rules you define on accounts you own and control. Nothing here is trading advice, and no automation setup prevents losses.