TLDR: If TradingView strategy alerts are not working, check whether the expected event happened on a realtime bar, whether the alert is active and unexpired, whether it uses order fills or alert() calls, and whether the strategy changed after the alert was created. TradingView saves a server-side copy of the strategy, inputs, symbol, and timeframe when an alert is created; later chart changes do not update that copy. Alerts based on alert() calls also stop if they trigger more than 15 times in three minutes. Recreate stale alerts and validate them before troubleshooting webhooks or brokers.
Stop Executing Trades By Hand.
UMT Automator turns your TradingView or NinjaTrader strategy into automatic, hands-free execution — no code, no webhooks, no missed signals. Prefer a ready-made edge? Browse UMT's tested Strategies & Indicators built for both platforms.
Free 7-day trial on the Automator · No credit card required
How TradingView Strategy Alerts Actually Run
A strategy alert does not keep reading the chart currently open in your browser. TradingView creates a server-side copy of the strategy and its context when the alert is created.
The saved context includes:
- The strategy script.
- The input settings.
- The chart's primary symbol.
- The chart timeframe.
The copy runs independently on TradingView's servers. This design lets alerts run when the user's browser is closed, but it also means changing the chart does not change the running alert.
12 Checks When TradingView Strategy Alerts Are Not Working
1. Check the Alert Log
Confirm whether the event is missing entirely or present with a delivery error. No log entry points to strategy or alert configuration. A log entry with failed Webhook status points to delivery.
2. Confirm the Event Happened in Realtime
TradingView alerts trigger on realtime bars. Historical orders that appear when a strategy recalculates do not send retroactive alerts.
3. Recreate the Alert After Strategy Changes
If you changed code, inputs, symbol, or timeframe, delete the old alert and create a new one. The old server-side copy still uses the earlier context.
4. Check the Selected Event Type
Strategy alerts can use order-fill events, alert() function calls, or both. Select an event the strategy actually produces.
5. Check Alert Frequency
Frequency and strategy calculation settings affect when alert() calls execute. A bar-close configuration will not behave like an intrabar event.
6. Check Expiration
Verify the alert is still active and its expiration date has not passed.
7. Check Fire-Control Stoppage
TradingView states that an alert based on alert() calls stops automatically if it triggers more than 15 times within three minutes. Rapid strategy behavior can therefore disable the alert.
8. Check Pine Script Errors
A runtime or calculation error can interrupt the strategy. Review chart and alert messages for script problems.
9. Check Repainting and Intrabar Logic
A condition visible while a bar was forming may disappear by the close. Historical recalculation may also differ from realtime tick behavior.
10. Compare Chart and Alert Time Zones Carefully
Match timestamps using the chart, exchange, Alert log, and broker time zones. An apparent missing alert may be a timestamp mismatch.
11. Confirm the Notification Action
The strategy event can occur while the desired popup, email, app notification, sound, or webhook action is disabled.
12. Confirm the Correct Account and Layout
Users with multiple TradingView accounts, browser profiles, layouts, or duplicate alerts can inspect the wrong configuration. Name alerts with the strategy version, symbol, timeframe, and destination.
Order Fill Events vs alert() Calls
| Event | What triggers it | Common mistake |
|---|---|---|
| Order fills | The TradingView broker emulator fills a strategy order | Assuming it confirms a live broker fill |
alert() calls |
The Pine code executes an alert call | Selecting it when the strategy has no applicable call |
| Both | Either event type | Sending duplicate or differently formatted messages downstream |
Order-fill events are based on the strategy's simulated broker emulator. They are useful automation triggers, but they are not feedback from a live brokerage account.
Why the Alert and Chart Show Different Orders
Differences may come from stale saved settings, calc_on_every_tick, recalculation after fills, intrabar price assumptions, repainting, or a chart that was changed after alert creation.
Record the strategy version and settings when creating the alert. If reproducibility matters, export or screenshot the configuration and include a version number in the alert name.
What to Do After the Alert Starts Working
An alert appearing in the log proves that TradingView created the notification. It does not prove a webhook delivered or a broker order was placed.
Next, check:
- Webhook status.
- Receiving-service signal log.
- Final rendered message.
- Symbol and quantity mapping.
- Broker order or rejection log.
Use TradingView Alert Triggered but No Broker Order Was Placed for the downstream checks.
Automate Strategy Activity Without Webhook Alerts
Ultra Mega Trader Automator monitors supported TradingView strategy activity in the active browser and works with the broker connection opened inside TradingView. It does not require the user to create webhook URLs, JSON order messages, or an external receiver.
UMT still requires the correct strategy, chart, broker, quantity, and order settings. TradingView and UMT must remain open. Paper trading is necessary because simplifying delivery does not fix incorrect strategy logic.
Want to test your TradingView strategy without building a webhook chain? Start a free seven-day UMT trial by contacting support@ultramegatrader.com.
TradingView Strategy Alerts FAQ
Why is my TradingView alert using old settings?
The alert runs from the copy saved when it was created. Delete and recreate it after changing the strategy, inputs, symbol, or timeframe.
Why did my strategy alert stop?
Check expiration, manual stoppage, script errors, and the rule that stops alert()-based alerts after more than 15 triggers in three minutes.
Why do historical orders not trigger alerts?
Alerts trigger in realtime. Historical strategy calculations do not send retroactive notifications.
Does UMT require strategy webhook alerts?
No webhook URL or JSON message is required in UMT's browser-based workflow. A correctly configured TradingView strategy is still required.
Sources
- TradingView: Strategy Alerts
- TradingView Pine Script Documentation: Alerts
- TradingView: Alerts on alert() Function
- TradingView: Alert and Chart Mismatches
Educational content only. Strategy alerts and simulated orders do not guarantee live broker orders, execution prices, or profitability. Validate the complete workflow in paper trading.
