TradingView alerts not triggering? 9 checks before you blame the indicator
Most missed alerts come from a workflow mismatch, not a broken script. Check the symbol and timeframe, the exact condition, the alert frequency, whether the signal only finalizes at bar close, and whether you changed settings after the alert was created. If you want a cleaner TradingView workflow from setup to alerting, start with the TradingWhale indicators overview and pricing page.
For current indicator plans and pricing, use the overview page above as of March 8, 2026. This guide focuses on troubleshooting, signal finalization, and safe testing, not trade outcomes.
Quick takeaway: Start with the boring checks. TradingView alerts are saved with the symbol, timeframe, script settings, condition, frequency, timer, and delivery options that existed when you created them. If any of those changed later, or if the alert was allowed to fire on a live candle, the chart you see now may not match what the server saw when the alert should have fired.
Best default: for most retail TradingView workflows, use final indicator settings, prefer cleaner bar-close logic when the signal is only valid at close, then verify the whole path in replay and paper trading before relying on push notifications or webhooks.
The 9 checks to run before you blame the indicator
Check 1: Confirm the symbol and timeframe match the workflow you meant to alert
Alerts on indicators depend on the chart interval because the script is calculated on that interval. A 15-minute alert created on EURUSD is not the same as a 1H alert on EURUSD, and neither matches a BTCUSD chart just because the layout looks similar. Start by checking the alert name against the chart you intended to monitor.
Check 2: Make sure you selected the exact condition, not the closest-looking one
Many traders create the alert from the right chart but pick the wrong dropdown option. Verify the script name, the specific alert condition, and whether you created an indicator alert, a strategy alert, or a basic price alert. One wrong condition can make the alert appear dead when it is simply listening for something else.
Check 3: Re-check the frequency setting
Once Per Bar can fire while the current candle is still building. Once Per Bar Close waits for the candle to close. If you expected a bar-close confirmation but saved the alert on a live-candle setting, the trigger may have happened earlier than the final chart makes obvious. If you are unsure which fits your workflow, compare the setups on the TradingWhale indicators overview and pricing page and then standardize your alert timing.
Check 4: Verify when the signal actually becomes final
This is where traders confuse alert failure with signal timing. Some conditions only make sense after the bar closes. Others can shift during the live candle, especially when higher-timeframe data or open-bar highs and lows are involved. If the signal is only trustworthy at bar close, the alert needs to match that rule. For a fuller explanation of signal finalization and chart changes after reload, use the TradingView indicator repainting guide.
Check 5: Ask whether you changed indicator inputs after creating the alert
This is one of the most common misses. TradingView saves the alert with the script settings that existed when you created it. If you later changed the lookback, smoothing, timeframe input, symbol source, or confirmation filter on the chart, the old alert keeps using the old version until you delete it and create a fresh one.
Check 6: Open Alert Manager and inspect the status, timer, and history
An alert may be stopped, expired, or auto-disabled if it triggered too often. Look for a disabled state, an expiration that already passed, or a log entry that shows the alert was firing far more frequently than intended. A stopped alert looks silent from the outside, but the real problem is usually condition design or frequency choice.
Check 7: Test the delivery path, not just the trigger logic
Sometimes the alert fired, but the message never reached you. Check whether app notifications are enabled, whether you are logged into the correct TradingView account on mobile, whether email notifications still work, and whether any webhook endpoint is receiving the payload you expect. Trigger logic and notification delivery are two separate points of failure.
Check 8: Review repainting, offsets, and higher-timeframe logic
Indicators that reference other timeframes or use offset-style plotting can look different after the chart refreshes. That can make a correctly fired live alert feel wrong in hindsight. If your workflow uses confirmation across timeframes, keep the setup simple and journal exactly when the alert fired versus what the final chart looked like later.
Check 9: Reproduce the setup in replay, then paper trade it
The fastest way to find the real failure point is to recreate the chart, re-create the alert, run the setup through replay, and then watch it in a live session with no capital at risk. That process tells you whether the problem is script logic, alert timing, or delivery. It also prevents you from making changes blindly when the workflow itself is the issue.
Why an alert can look wrong even when it fired correctly
| What you notice | What is often happening | What to check next |
|---|---|---|
| The alert never arrived | The alert may be stopped, expired, or the notification path failed. | Alert Manager status, timer, app login, push permissions, email, webhook log. |
| The alert fired, but the chart does not show the setup now | The condition may have been true on the live candle and no longer be true after close or after refresh. | Frequency, bar-close confirmation, higher-timeframe logic, repainting notes. |
| The chart setup changed, but the alert still behaves the old way | The alert is still using the snapshot saved when it was created. | Delete and recreate the alert with the current settings. |
| The alert arrived later than expected | Bar-close confirmation, exchange timing, or strategy-order timing can create a visible delay. | Frequency, market activity, and whether the alert is indicator-based or strategy-based. |
This is also why a clean troubleshooting workflow matters more than random tweaks. If you change the condition, the indicator, the timeframe, and the notification path all at once, you lose the ability to see what actually fixed the problem. Keep one chart, one alert, one test window, and one journal note for each change. If you want a cleaner set of TradingView-native scripts to work from, use the TradingWhale indicators overview and pricing page as your central setup hub.
Common pitfall: treating a live-candle alert like a closed-candle signal.
That mismatch creates many of the “it did not trigger” complaints because the trader is checking the final chart instead of the live condition that existed when the alert server evaluated it.
Common pitfall: changing script inputs and assuming the existing alert updated.
It did not. Recreate the alert whenever you change the script inputs that matter to the signal.
TradingView setup: conditions, timeframes, frequencies, and saved settings
- Condition: choose the exact indicator or strategy trigger, not just the script name.
- Timeframe: use the chart interval you actually trade or review. Alerts on indicator plots depend on interval.
- Frequency: match the alert to signal finalization. Use bar-close confirmation when the setup only counts after the candle is final.
- Saved settings: if you changed script inputs after creating the alert, recreate it.
- Timer and status: verify the alert is active, not expired, and not auto-disabled.
- Message and destination: test app, email, and webhook delivery separately from chart logic.
A practical way to reduce troubleshooting loops is to standardize the workflow. Use one watchlist scan, one confirmation layer, and one execution-oriented script instead of stacking too many overlapping signals. For example, the Multi-Symbol Indicator Screener can narrow the watchlist, and Entry & Exit Optimizer can help structure the chart review and alert timing more cleanly.
Common failure modes: notifications, webhooks, stopped alerts, and strategy timing
- Push notifications are off: the alert may have fired, but your phone never showed it.
- Wrong account session: your desktop and mobile may not be using the same TradingView login.
- Webhook endpoint failed: the chart side worked, but the receiving app did not accept or log the request.
- Alert was triggered too often and stopped: an overactive condition can disable the alert until you fix it and recreate a cleaner version.
- Strategy timing mismatch: a strategy alert can appear delayed compared with the Strategy Tester chart because realtime and historical order handling are not always displayed the same way.
Warning: do not solve this by loosening every rule at once. A noisy alert condition can look “fixed” simply because it now fires constantly. The better fix is to reduce false triggers by clarifying the condition, using the proper frequency, and removing overlapping logic that turns one setup into three slightly different alerts.
If your goal is fewer charts and fewer manual checks, build one clean alert stack and document exactly when the message should fire. That is a better path than adding more scripts out of frustration. You can browse the current subscription options on the TradingWhale indicators overview and pricing page and then keep your live workflow narrow and testable.
Alert recipe: one cleaner way to reduce missed or confusing alerts
Step 1: Scan a limited watchlist with the Multi-Symbol Indicator Screener.
Step 2: Open only the charts that match your planned timeframe for the day or session.
Step 3: Apply one execution-focused script such as Entry & Exit Optimizer with the exact inputs you plan to keep.
Step 4: Create one alert per condition with a clear message template that includes timeframe and setup name.
Step 5: Use bar-close confirmation when the setup only matters on a confirmed candle. Keep open-candle alerts only for workflows where you will still review the chart manually.
Step 6: Run the same chart through replay and then paper trade the alerts before relying on the workflow live.
This recipe is intentionally boring. Boring is good for alerts. The more variables you lock down before saving the alert, the easier it is to tell whether the alert really failed or the workflow simply changed underneath it.
How to test safely before you trust the alert
Start with replay on the exact symbol and timeframe where the alert failed. Re-create the alert conditions, step forward bar by bar, and note whether the signal appears during the open candle or only after close. Then paper trade the same setup for several sessions so you can compare live notifications with what the chart looked like at that moment.
Testing rule: do not judge the alert by a single example. Check multiple market states, including trend, range, and event-driven volatility. If you use any historical performance view or script-based testing, remember the limits: slippage, fees, spread, overfitting, lookahead bias, and market regime changes can all make a clean-looking setup behave differently in live conditions. For risk structure, journaling, and drawdown awareness, keep the drawdown guide close to the workflow.
FAQ
Why did my alert fire yesterday but not today with the same chart open?
The chart may look similar, but the alert is tied to the exact symbol, timeframe, script settings, and trigger logic saved when you created it. If any of those changed, or the condition only existed during the live candle, the outcomes can differ.
Do I need to recreate the alert after changing indicator settings?
Yes. If the changed input affects the signal, delete the old alert and create a fresh one so the server-side copy matches the chart you are actually using.
Can a bar-close alert still arrive a little late?
Yes. Bar-close alerts can arrive slightly after the exact close because the system needs confirmation that the previous bar is truly complete. This is most noticeable on symbols with infrequent or late-reported trades.
What if the alert fired but I never got the phone notification?
Treat that as a delivery problem first. Check app notification permissions, your TradingView login on mobile, device battery restrictions, and whether email or webhook delivery worked at the same time.
How do I know whether the issue is repainting or just bad alert timing?
Run the alert in replay and note whether the setup appears and disappears on the open candle. If the live condition changes before close, that points to timing and open-bar behavior. If the chart itself changes after refresh or with higher-timeframe requests, repainting may be part of the problem.
Related answers
- What Is Trading Indicator Repainting?
- Entry & Exit Optimizer on TradingView
- Multi-Symbol Indicator Screener for TradingView
- Drawdown in Trading: A Comprehensive Guide
Final CTA
If your current alerts feel inconsistent, the fix is usually a cleaner process, not more chart clutter. Standardize the timeframe, lock the signal settings, match the alert frequency to signal finalization, and test the whole path before relying on it live. To build that workflow with TradingView-native scripts, go back to the TradingWhale indicators overview and pricing page, choose the indicator stack that fits your charts, and then install the indicators and set your alerts the clean way.
Disclaimer
This content is for informational and educational purposes only and is not financial, investment, legal, or tax advice. Trading and investing involve risk, including the possible loss of all capital. Past performance is not indicative of future results. Always do your own research and consider consulting a licensed financial professional before making trading decisions.
See TradingWhale’s Disclaimer and Terms and Conditions.
