A TradingView alert that silently fails to fire is one of the most frustrating things that can happen to a trader — you set it up, assume it’s watching the market for you, and only find out it never triggered after the move already happened. Here are the nine most common reasons, roughly ordered from most to least frequent, and how to fix each one.
1. The Alert Is Waiting for a Bar to Close
TradingView alerts can trigger “Once Per Bar Close” instead of in real time. If your condition was met mid-candle but the alert is set to bar close, it waits until the current candle fully closes before firing — which can be minutes away on a 5-minute chart, or hours on a 4-hour chart. Open the alert’s settings and switch the trigger frequency to “Once Per Bar” or a realtime option if you need it immediately.
2. The Alert Already Expired
Alerts created with an end date deactivate automatically once that date passes, and they won’t warn you when they do. If an alert that used to work has gone quiet, check whether it has an expiration date set and extend it or remove it.
3. It Was a “Once” Alert That Already Fired
Alerts set to trigger only once deactivate themselves after the first trigger. If you expected it to keep watching the same condition and it stopped, check whether it’s set to fire once or every time, and switch to “Once Per Bar” (or similar) if you want it to keep monitoring.
4. A Typo in the Webhook URL
This is the single most common cause of a webhook alert that looks correctly configured in TradingView but never actually delivers anywhere. A missing character, an extra space at the start or end, or an outdated URL from a previous account will all cause the request to fail silently on TradingView’s side. Delete the URL field and paste your current webhook URL from TradeBeep fresh, rather than editing the existing text.
5. Your TradingView Plan Doesn’t Include Webhooks
Webhook alerts are gated behind TradingView’s paid plans. If your plan was recently downgraded, or you’re on the free tier, the webhook field either won’t appear or won’t actually send anything even if you fill it in. Check your current plan against TradingView’s feature comparison to confirm webhooks are included.
6. You Hit TradingView’s Alert Limit
Every TradingView plan caps the number of active alerts you can have running at once. Once you’re at the limit, new alerts either fail to save or silently don’t activate. Check your active alert count against your plan’s limit and remove any old alerts you no longer need.
7. Your Phone Is Blocking the Notification
If TradingView’s alert log shows the alert actually fired but you never heard anything, the problem has moved from TradingView’s side to your phone’s. Check that notifications are enabled for TradeBeep specifically, and that Do Not Disturb or a focus mode isn’t silencing it.
8. Battery Optimization Is Killing Background Delivery
Android and iOS both aggressively manage which apps are allowed to run in the background to save battery, and an alarm app that gets “optimized” can be delayed or stopped from ringing entirely while your screen is off. On Android, look for TradeBeep in your battery settings and set it to “unrestricted” or exclude it from battery optimization. On iOS, make sure Background App Refresh is enabled for TradeBeep.
9. The Alert Condition Genuinely Wasn’t Met
It sounds obvious, but it’s worth ruling out last: double-check the condition itself against the actual price action. A condition based on the wrong timeframe, an indicator setting that changed, or a simple off-by-one in your target price will all produce an alert that’s technically working correctly — just not for the situation you expected.
When in doubt, test the chain end to end: set a temporary alert with a condition you know will fire in the next few minutes, and confirm TradeBeep rings before you trust a real trading alert to it.
If you haven’t connected TradingView to TradeBeep yet, start with our step-by-step webhook setup guide — most of the causes above are easiest to avoid by getting the initial setup right.
Frequently Asked Questions
Why did my TradingView alert fire once and then stop working?
TradingView alerts created with an expiration date deactivate automatically once that date passes, and alerts set to trigger "Once Per Bar" or "Once" will fire a single time and then need to be manually reset. Check the alert's settings — the expiration date and trigger frequency are the two most common culprits.
Why is my webhook alert delayed by several minutes?
This is almost always the alert's frequency setting, not the webhook itself. "Once Per Bar Close" waits for the current candle to fully close before firing, which can be minutes (or longer, on higher timeframes) after the price condition was actually met. Switch to "Once Per Bar" or realtime triggering if you need it to fire immediately.
My alert shows as active in TradingView but I never get notified — why?
If the alert is firing on TradingView's side (check the alert log) but you're not getting a notification, the problem is almost always downstream: a typo in the webhook URL, or your phone silencing/blocking the notification. See the phone-side fixes above — notification permissions and battery optimization are the most common causes.