TradingView Alerts Not Firing: 8 Fixes That Actually Work

TradingView alerts not firing is the most frustrating problem in automated trading. You set up a perfect strategy, configure the webhook, wait hours for the signal — and nothing. No notification. No webhook. No trade. Meanwhile, price hit your level exactly and moved 50 pips without you.

This issue appears on every trading forum weekly. The causes range from simple plan limitations to subtle indicator bugs. Here are 8 fixes ranked from most common to most obscure.

TradingView Alerts Not Firing: Fix 1: Check Your Alert Limit

The number one reason alerts stop firing: you have hit your TradingView plan's active alert limit.

• Free plan — 5 active alerts
• Essential — 20 active alerts
• Plus — 100 active alerts
• Premium — 400 active alerts
• Expert — 800 active alerts

When you exceed your limit, new alerts silently fail to activate. TradingView does not always show a clear error — it may appear to save the alert, but it never fires. Check your active alert count in the Alerts panel (bell icon). If you are at the limit, delete old alerts before creating new ones.

Fix 2: The Alert Already Fired — "Only Once" Trap

By default, TradingView alerts can be set to trigger:

• Only Once — fires once, then auto-expires
• Once Per Bar — fires once per bar when condition is true
• Once Per Bar Close — fires once when bar closes with condition true
• Every Time — fires on every tick the condition is met

If your alert was set to "Only Once" and it already triggered (even if you missed it), it will not fire again. Go to the Alerts panel, check the alert's status — if it shows "Triggered" or is grayed out, recreate it.

Fix 3: The Indicator Was Modified or Removed

If you create an alert based on a custom indicator, then modify or remove that indicator from the chart, the alert becomes orphaned. It references a condition that no longer exists in the expected state.

The fix: delete the alert, re-add the indicator to the chart, verify it works correctly, then recreate the alert. If you updated the indicator's code, all alerts based on the old version must be recreated.

Fix 4: Condition Already True When Alert Was Created

TradingView alerts trigger on state changes, not static conditions. If you create an alert for "RSI crosses above 70" while RSI is already at 75, the alert will not fire because the crossing already happened.

The alert will fire the next time RSI drops below 70 and then crosses back above it. This catches many traders off guard — they think the alert is broken when it is simply waiting for the next crossing event.

How to Verify

Before creating the alert, check if the condition is currently true on the chart. If it is, you need to wait for it to reset (become false) before it can trigger. Alternatively, use a condition like "RSI Greater Than 70" with the "Every Time" trigger to get an immediate notification — but be aware this will fire repeatedly.

Fix 5: Wrong Symbol or Timeframe

Alerts are bound to the specific symbol and timeframe that was active when you created them. If you:

• Created the alert on EURUSD 15-minute chart
• Later switched to EURUSD 1-hour chart
• Expected the alert to fire on the 1-hour chart

...the alert is still monitoring the 15-minute chart. Open your Alerts panel, click any alert, and check its symbol/timeframe binding. Delete and recreate if it is bound to the wrong context.

Fix 6: Server-Side Alert Processing Issues

TradingView processes alerts on their servers, not in your browser. This means:

• Closing your browser does not stop alerts (they keep running server-side)
• But TradingView server maintenance can temporarily delay or drop alerts
• During high-load periods (major news events), alert processing slows down

If your alerts stopped firing around the same time as a TradingView platform update or during a major economic release, check the TradingView status page for known issues. Sometimes the fix is simply waiting for their infrastructure to stabilize.

Fix 7: Webhook URL Issues (Separate from Alert Issues)

If your alert fires (you see the popup/email notification) but the webhook does not send, the problem is the webhook configuration — not the alert itself. Common webhook failures:

• URL typo — one wrong character means no delivery. Copy-paste carefully.
• Trailing space — an invisible space at the end of the URL breaks it.
• HTTP vs HTTPS — TradingView requires HTTPS webhook endpoints. HTTP will fail silently.
• Server timeout — your endpoint must respond within 3 seconds. Slow servers get timeouts.
• Plan requirement — webhooks require the Essential plan or higher. Free plans cannot send webhooks.

For detailed webhook troubleshooting, see our TradingView webhook not working guide.

Fix 8: Pine Script Alert Condition Bugs

If your alert uses a custom Pine Script indicator's alertcondition() function, the bug may be in the script itself:

• Condition never becomes true — the logic has a flaw that prevents the condition from ever triggering
• Repaint issue — the indicator repaints on historical bars (shows signals that did not exist in real-time), but in live mode the condition never fires
• Version mismatch — Pine Script v3/v4 scripts may behave differently when run on TradingView's current engine
• Variable scoping — the condition references a variable that is calculated differently in real-time vs. historical mode

Debug by adding a simple plotshape() to visualize when your alert condition becomes true. If you see shapes on historical bars but not on current bars, your indicator has a repaint problem.

Nuclear Option: Delete Everything and Restart

If none of the above fixes work, try the clean slate approach:

1. Delete all alerts on the symbol
2. Remove the indicator from the chart
3. Refresh the page (hard refresh: Ctrl+Shift+R)
4. Re-add the indicator
5. Verify the indicator shows correct signals on recent bars
6. Create a new alert with the correct condition and trigger type
7. Test with a condition that should fire within minutes (e.g., price crossing a level that is very close to current price)

If this test alert fires correctly and delivers the webhook, your setup is working. The issue was a stale alert state — corrupted by indicator updates, plan changes, or TradingView server issues.