TLDR: A TradingView webhook cannot fire unless the underlying alert creates a realtime trigger. Open the Alerts Log first. If there is no trigger at the expected time, check the alert's status, expiration, saved settings, symbol, timeframe, condition, frequency, strategy event type, and Pine logic. If a trigger appears but Webhook status failed, the alert did fire and the problem is delivery, not the trigger.
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
Traders often describe any missing automated action as a webhook that “did not fire.” That wording can hide two separate systems. TradingView first evaluates an alert condition. Only after that condition triggers can TradingView send an HTTP POST to the configured webhook URL.
This guide focuses on the first system: why the alert event never appeared. If your Alerts Log already contains the trigger, use the companion TradingView webhook not sending guide to troubleshoot the URL, firewall, TLS, server response, or three-second delivery limit.
If webhook alerts are the recurring obstacle between a TradingView strategy and broker execution, UMT Automator offers a browser-based workflow for eligible strategies without a user-configured webhook, JSON payload, broker API key, or custom middleware server. First, however, confirm whether your strategy or alert is producing the event you expect.
Did the Alert Fail to Trigger, or Did the Webhook Fail to Send?
Find the expected time in TradingView's Alerts Log and classify the incident:
| Evidence | Meaning | Next step |
|---|---|---|
| No alert entry exists | The alert condition did not produce a trigger. | Work through the 12 alert checks below. |
| Alert entry exists and Webhook status failed | The alert fired, but delivery failed. | Record the exact delivery error and troubleshoot the endpoint. |
| Alert entry exists and Webhook status succeeded | The destination returned a successful HTTP response. | Check the receiving application, queue, broker request, rejection, and fill records. |
Do not change the webhook server when no alert event exists. The server cannot receive a POST that TradingView never had a reason to create.
1. Is the TradingView Alert Still Active?
Open Alert Manager and inspect the alert's current status. TradingView distinguishes several states:
- Active: the alert is running.
- Stopped after triggering: an “Only once” alert already fired.
- Stopped manually: the alert was paused or disabled.
- Expired: the configured timer ended.
An alert can look correctly configured when opened, yet remain unable to fire because its status is stopped. Confirm the status before examining Pine code or server logs.
TradingView also states that an old alert may be automatically deactivated when all three conditions apply: it was created more than one year ago, it has not triggered for more than one year, and it has not been edited for more than one year.
2. Did “Only Once” Already Stop the Alert?
An alert configured as “Only once” stops after its first trigger. The first event may be easy to miss if it occurred during testing, outside your intended session, or before the webhook receiver was ready.
Review the entire available log for that alert instead of only the expected trade time. If it fired earlier, create a new alert with the frequency that matches your actual intent. Do not resume or recreate an execution alert without checking whether the earlier event produced a paper or live order.
3. Did the Alert Expire?
TradingView alerts can have an expiration date. Open-ended availability varies by alert type and plan. If a webhook worked previously and then went silent at a predictable date or time, inspect the expiration setting before assuming an outage.
When replacing an expired alert, verify every setting again. A saved preset can reduce repetitive setup, but TradingView documents that webhook URLs are not saved in alert presets. You must confirm the Webhook URL action separately.
4. Is the Correct Condition Selected?
The alert must monitor the intended source and operator. Verify all of the following:
- The correct price series, indicator, drawing, chart pattern, or strategy is selected.
- The operator is correct, such as Crossing, Crossing Up, Greater Than, or Less Than.
- The threshold is on the correct side of the current value.
- The alert is attached to the intended script instance when the chart has similar indicators.
- The selected strategy event is order fills,
alert()calls, or both, as intended.
Crossing Up is not the same as Greater Than. For example, if price is already above the threshold when a Crossing Up alert starts, it may need to move below and then cross upward before the condition becomes true.
5. Are the Symbol, Timeframe, and Chart Type Correct?
TradingView explains that price alerts on a data series are not interval-dependent, but alerts based on indicators, strategies, drawings, and certain chart types can depend on the selected timeframe.
Check the saved alert's symbol and interval, not only the chart currently visible in your browser. Also confirm whether the alert was created on standard candles or a non-standard chart such as Heikin Ashi, Renko, Range, Line Break, Kagi, or Point and Figure. Different chart construction can change when a condition becomes true.
For futures, verify that the alert uses the intended continuous contract or specific expiry. For any market, confirm the data feed and session settings relevant to the script.
6. Is the Alert Running an Older Copy of Your Settings?
This is one of the most important TradingView alert behaviors to understand. TradingView states that changing an indicator's parameters after creating an alert does not update the existing alert. It continues using the old settings.
Strategy alerts go further. When you create one, TradingView creates a server-side copy of the strategy, its inputs, chart symbol, and timeframe. That copy runs independently from the strategy displayed in your browser. Later chart or strategy changes do not update the alert's saved copy.
If you changed an input, symbol, timeframe, strategy property, or script version, delete the old alert and create a new one from the verified configuration. Give the new alert a name that includes the strategy version, symbol, timeframe, and creation date so you can identify stale instances later.
7. Are You Expecting an Alert from a Historical Bar?
TradingView strategy alerts trigger for orders executed in realtime, not for orders calculated on historical bars. Adding a strategy to a chart can populate Strategy Tester with many earlier trades, but those historical trades do not generate new alert notifications.
After creating the alert, wait for a new realtime event that satisfies the condition. Do not use a historical chart marker as proof that a webhook should have fired after the fact.
8. Is the Alert Waiting for the Bar to Close?
Alert frequency changes when TradingView is allowed to trigger:
- Once per bar: no more than one trigger during a bar when the condition is met.
- Once per bar close: the bar must close with the condition satisfied.
- Once per minute or every time: availability and behavior depend on the alert type.
- Strategy alert frequency: often comes from the script and strategy execution behavior rather than the dialog.
A condition can become true during the bar and become false before the close. In that case, an alert set to Once Per Bar Close will correctly remain silent. That is not a webhook failure.
9. Does the Strategy Calculate Intrabar?
TradingView strategy scripts calculate once at the closing tick of each realtime bar by default. Indicators normally recalculate as new realtime updates arrive, but strategies do not behave that way unless their execution settings permit intrabar calculation.
A strategy using alert() may therefore appear late or silent during an open bar even when the price briefly crossed a level. The strategy might not evaluate that condition until the bar closes.
Developers can use calc_on_every_tick or related settings to change strategy execution. That is not a universal fix. Intrabar calculation can create differences between realtime and historical results, affect repainting behavior, and change alert frequency. Test any such change as a strategy change, then recreate the alert so its server-side copy includes the new configuration.
10. Did You Select the Correct Strategy Alert Event?
A Pine strategy alert can listen for:
- Order-fill events.
-
alert()function calls. - Both order fills and
alert()calls.
If the alert is configured for alert() calls only, a broker-emulator order fill does not automatically create that event unless the script also executes the relevant function call. If it is configured for order fills only, a custom alert() call is not enough.
TradingView notes that order-fill alerts execute when the broker emulator fills the strategy order. This is different from a condition becoming true or a strategy merely placing an unfilled limit order.
11. Does the Pine Script Actually Create an Alert Event?
The Pine function alertcondition() defines a condition that can appear in the Create Alert dialog. It does not create an active alert by itself. The user must still create an alert instance and select the intended condition.
For alert():
- The script's logic must execute the function call on a realtime update.
- The alert must select “Any alert() function call” or the corresponding strategy option.
- The function's frequency must permit a trigger on that execution.
- A runtime error can halt script execution before the call is reached.
- Conditional branches, session filters, date filters, position state, and
navalues can prevent the call from executing.
If you control the source code, add temporary Pine Logs around the condition and alert call. Record the input values and each Boolean component separately. Remove or reduce diagnostic logging after the issue is understood.
12. Did TradingView Stop a High-Frequency Script Alert?
TradingView states that a script alert automatically stops if it triggers more than 15 times within three minutes. A fast loop, intrabar logic, repeated alert() calls, or an unexpectedly broad condition can hit this limit.
Check Alert Manager for the stopped state and review the preceding log entries. Do not simply restart the alert. First fix the condition or frequency that produced the burst, then create a controlled paper-trading test. Restarting unchanged logic can stop the alert again or send repeated downstream instructions.
Could Repainting Make It Look Like the Webhook Never Fired?
On an open realtime bar, values such as high, low, close, volume, and indicator outputs can change with every update. TradingView's execution model uses rollback and recalculation during that open bar. A signal can appear temporarily and then disappear before the bar closes.
This creates two confusing situations:
- An intrabar alert fires, but the chart no longer shows the signal after the bar closes or the script reloads.
- A trader sees a temporary chart condition, but a Once Per Bar Close alert never fires because the condition is false at confirmation.
Neither situation proves that webhook delivery failed. Choose confirmed-bar or intrabar behavior deliberately, understand the script's repainting characteristics, and compare the alert log with realtime evidence rather than a refreshed historical chart.
Check TradingView Status Before Changing a Working Configuration
TradingView publishes an official status page for Alerts, Pine Script studies and strategies, data feeds, and other services. At the time of research on August 26, 2026, the page reported all systems operational, including Alerts and Pine Script studies and strategies.
Service state can change. Check the current status and incident history when multiple unrelated alerts fail together. If one alert on one condition is silent while other alerts continue to work, configuration or script behavior is usually the more productive place to start.
A Safe Test for an Alert That Is Not Firing
- Use paper trading or disconnect downstream live execution.
- Duplicate the intended setup with a clearly named test alert.
- Choose a condition you can trigger once in a controlled way.
- Enable an ordinary notification action in addition to the webhook so the trigger is visible independently.
- Wait for a new realtime event.
- Confirm the event in the Alerts Log.
- Only after the trigger exists, inspect Webhook status and receiver logs.
- Change one setting at a time and record the result.
Do not repeatedly test against a live broker. A duplicate alert, restart, or delayed downstream process can create an unintended order after you believe the first test failed.
How UMT Avoids TradingView Webhook Alert Configuration
UMT Automator is software that connects eligible TradingView strategy activity with broker-side automated order execution through an active browser workflow. It does not require the user to create a TradingView webhook alert, format JSON, manage a webhook server, or provide broker API keys to UMT.
UMT still needs valid strategy activity. It cannot make a strategy produce an entry or exit that its logic never generates. The current setup requires a TradingView strategy, a compatible desktop browser, a supported broker connection through TradingView, the correct chart and strategy layout, an active TradingView tab, and stable internet. The UMT Getting Started guide also requires the Strategy Tester List of Trades and its Signal column to remain visible for the documented workflow.
The current free seven-day UMT Automator trial lets a qualified trader test this workflow in paper trading. During the trial, verify that UMT observes the intended new strategy entries and exits, uses the correct account and quantity, fits your strategy's order behavior, and remains compatible with how you operate the browser. Do not use live capital for the first validation.
Want to test strategy automation without building webhook alerts? Review the UMT Automator requirements and current plans, then follow the UMT Getting Started guide. Request the free seven-day trial at support@ultramegatrader.com.
Frequently Asked Questions
Why is my TradingView webhook not firing?
The underlying alert may be stopped, expired, configured for the wrong condition, using old saved settings, waiting for a bar close, listening to the wrong strategy event, or blocked by Pine logic. Check for an alert entry before troubleshooting the webhook server.
Why does my TradingView chart show a signal but no alert fired?
The signal may be historical, may have appeared only intrabar, or may come from chart settings that differ from the alert's saved server-side copy. Strategy and indicator changes made after alert creation do not automatically update the existing alert.
Do historical TradingView strategy trades trigger webhooks?
No. TradingView states that strategy alerts trigger for orders executed in realtime, not orders on historical bars.
Why did my TradingView strategy alert stop?
It may have expired, used an Only Once setting, been stopped manually, or exceeded TradingView's script-alert limit of more than 15 triggers in three minutes.
Does alertcondition() automatically create a TradingView alert?
No. It exposes a selectable alert condition. A user must still create an active alert instance from the Create Alert dialog.
Can UMT automate a TradingView strategy without a webhook?
Yes, for eligible browser-based workflows. UMT does not require a user-configured TradingView webhook, JSON message, broker API key, or custom middleware server. Review the current requirements and test with paper trading.
Risk and Reliability Notice
Automated trading depends on strategy logic, platform calculations, software, browser availability, internet connectivity, broker acceptance, and market conditions. Alerts, automation, broker orders, and fills are not guaranteed. Validate the full workflow in paper trading, use appropriate risk limits, monitor open positions, and maintain a manual procedure for stopping automation and managing orders.
Official Sources
- TradingView: Manage alerts
- TradingView: How to set up alerts
- TradingView: Strategy Alerts
- TradingView: Alerts on the alert() function
- TradingView: Differences between alert frequencies
- TradingView Pine Script: Execution model
- TradingView Pine Script Reference Manual
- TradingView: How to configure webhook alerts
- TradingView Status
- Ultra Mega Trader: Trade Automator for TradingView
- Ultra Mega Trader: Getting Started
