TradingView Help
TradingView Webhooks FAQ
Answers to common TradingView alert and webhook questions, checked against TradingView's own help pages and Pine Script documentation in October 2026. Plans and limits change, so check TradingView's pricing page before you buy.
Reviewed by PickMyTrade Trading Systems Team (Automated Futures & Execution Specialists) Last reviewed:
TradingView alerts and webhooks
18 answersWhy didn't my TradingView alert fire?
Run five checks from TradingView's Pine Script FAQ. First, confirm the alert is active and not expired, because created alerts do not fire after they expire. Second, open the alert log: an alert can fire without sending a notification. Third, check for repainting, which shifts when signals appear. Fourth, TradingView halts an alert that triggers more than 15 times in 3 minutes. Fifth, a script runtime error stops that script's alerts. Also, an alert runs on a saved copy of the script and its inputs, so after changing settings on your chart, delete the alert and create a new one.
Do TradingView alerts work in Bar Replay?
Existing server-side alerts keep using real-time data while the chart replays historical bars. Bar Replay does not replay those alerts, and you cannot create new server-side alerts in replay mode. Replay Trading is a separate historical simulation, not proof that a webhook reached your broker. For an automation test, use a supported demo connection with real-time alerts and check the resulting execution records. TradingView Bar Replay limitations
What is the difference between "Once per bar" and "Once per bar close" alerts?
"Once per bar" fires the first time the condition is true while the candle is still forming. "Once per bar close" waits for the candle to close and fires only if the condition is still true then. The trade-off: "Once per bar" is earlier but can fire on a signal that disappears by the close, for example an RSI cross that reverses before the bar ends, according to TradingView's Help Center. If you want alerts to match what the chart shows after the close, the Pine Script FAQ recommends "Once Per Bar Close".
Strategy alerts: what is the difference between "order fills" and "alert() function calls"?
They are the two trigger types for an alert on a TradingView strategy. "Order fills" fires whenever the strategy's simulated broker fills an order, such as an entry, exit, stop or target. "alert() function calls" fires only when the script runs an alert() call its author wrote. Per the Pine Script docs, strategies run alert() calls only at bar close by default, while alerts from order fill events "execute immediately", which the docs call "often more suitable for sending alerts to third parties for automation." If the script has no alert() calls, that option sends nothing.
Why can TradingView pyramiding differ from orders in my Tradovate account?
TradingView’s Pyramiding setting limits successive same-direction entries created by strategy.entry(); it does not control strategy.order(). PickMyTrade’s Tradovate alert settings are separate: pyramid controls stacking, while same_direction_ignore set to true ignores another same-direction alert when a position is already open. The reverse_order_close setting controls whether opposite positions are closed. A Pine pyramiding limit is therefore not proof of a matching live account limit. Review both configurations, generate the appropriate PMT message, and test a controlled sequence of same-direction and opposite-direction alerts in demo. Confirm orders and position size before enabling live automation.
Which TradingView placeholders belong in a PickMyTrade alert message?
Start with the message generated for your selected PickMyTrade broker and alert type. TradingView placeholders such as {{ticker}} and {{close}} supply alert values, while strategy-prefixed placeholders are for strategy alerts. PMT’s documented Tradovate strategy message uses {{strategy.order.action}} and {{strategy.order.contracts}}; an indicator alert should use its generated indicator message instead. If a custom strategy supplies an alert_message in its order calls, TradingView requires {{strategy.order.alert_message}} in the alert dialog to insert it; an order call without that message can produce an empty value. That advanced method does not replace the PMT-generated format automatically. Test the triggered message and broker result in demo before enabling live automation.
Do TradingView webhooks need a paid plan and two-factor authentication?
Yes to both, as of 5 Oct 2026. TradingView's pricing comparison table marks "Webhook notifications" as not included on the free Basic plan and included on Essential, Plus, Premium and Ultimate. Separately, the Help Center says webhook alerts are only allowed when two-factor authentication is enabled. So you need a paid plan and 2FA turned on in your TradingView account before you can use webhook alerts. TradingView also warns not to put login credentials or passwords in the webhook message body.
Why is my TradingView webhook not reaching my URL?
Check TradingView's documented webhook limits first. The Help Center says only ports 80 and 443 are accepted, requests are cancelled if the receiving server takes longer than three seconds to process them, and IPv6 is not supported. If your server has a firewall, allowlist the four TradingView IP addresses listed on that Help Center page. Then open the alert log and read the "Webhook status" column, which shows delivery failures. TradingView also notes webhooks may occasionally fail to reach the URL, so treat a webhook as a best-effort channel, not guaranteed delivery.
Does TradingView retry a failed webhook?
TradingView documents retries when the receiver returns HTTP 500–599, except 504. It waits five seconds and can resend three times, for up to four sends including the original. This is not a promise to retry every timeout or delivery failure. The retry concerns delivery to the webhook URL; it does not tell you whether a broker accepted or filled an order. Before manually resending, check TradingView’s Webhook status, PickMyTrade’s Alert Log and the broker’s orders and positions. A failed or delayed response alone is not evidence that no order exists.
Why can my TradingView alert arrive while a limit order remains unfilled?
Alert delivery, order acceptance and a trade fill are different steps. First check that the alert appears in PickMyTrade’s logs, then check the order status in your broker. An accepted limit order can remain working when its price conditions are not met or there is not enough available liquidity; even reaching the limit price does not guarantee a fill. A partial fill leaves some quantity unfilled, so compare filled and remaining quantity. If the broker rejected the order, use its rejection reason instead. Check the existing order before resending an alert so you do not unintentionally create another order.
How many indicators can I use on the free TradingView plan?
Two per chart. TradingView's pricing page, checked 5 Oct 2026, lists indicators per chart as 2 on Basic (free), 5 on Essential, 10 on Plus, 25 on Premium and 50 on Ultimate. The free plan is also tighter on alerts: the comparison table shows 3 active price alerts on Basic and marks technical alerts as not included. TradingView counts any alert built on an indicator, strategy or drawing as a technical alert, so alerts from an indicator need a paid plan. Plan limits change, so check the pricing page before you buy.
Can a TradingView strategy alert fire before the candle closes?
Yes, but there is a cost. By default a TradingView strategy calculates only when a bar closes. Turning on "On realtime bar tick" in the strategy's Script execution settings (calc_on_every_tick = true in code) lets it calculate on every price update, so orders and alerts can fire mid-candle. The Pine Script docs warn this can cause repainting in the strategy's orders and results, because after a reload, historical bars do not keep the intrabar ticks the strategy acted on. The backtest may then not show the trades your live alerts sent.
Does TradingView have a delay on alerts?
TradingView documents specific delay cases, not a general latency figure. Its Help Center says "Once Per Bar Close" alerts wait for the first trade of the next bar to confirm the close, so on thinly traded symbols they can arrive several seconds late; if no trades arrive, for example after a session closes, the server closes the bar 1 minute after its formal close. Strategy alerts can also look late in the Strategy Tester, because historical orders show the bar's open time, not the real fill time. We found no official TradingView figure for total alert-to-broker latency.
Is TradingView's futures data delayed on the free plan?
Yes for CME Group markets unless you add real-time data. TradingView's CME page states that all CME Group data is free on TradingView with a 10-minute delay, and real-time CME, CBOT, COMEX and NYMEX data is sold as a separate subscription. The Help Center adds a catch for traders who connect a broker: the order panel and buy and sell buttons use your broker's data, not TradingView's, so those quotes can still be delayed even after you buy real-time chart data. Check which feed your chart and order panel use before trading.
Do TradingView alerts still work if I close the chart or turn off my computer?
Yes. TradingView's Help Center says alerts are server-side, so you can close TradingView or leave the chart page and they keep working. When you create an alert on a script, TradingView saves a copy of the script, its inputs, the symbol and the timeframe, and runs that copy on its servers. The catch: later edits on your chart do not reach the running alert. If you change a setting, symbol or timeframe, delete the old alert and create a new one, or it keeps firing on the old settings.
How do I stop or delete a TradingView alert used for automation?
Open TradingView’s Alerts Manager, find the alert, and choose Stop for a pause or Delete to remove it. On mobile, long-press the alert to open these controls. Check its status after stopping it. Hiding the alert line or closing the chart is not the same as stopping the alert. Review existing orders and positions separately in your broker platform.
Can I send PickMyTrade webhook alerts from TradingView tick charts?
TradingView currently does not provide server-side alerts for tick-based intervals, so those charts cannot start the TradingView webhook-alert workflow used by PickMyTrade. A tick chart forms bars from a number of ticks rather than a fixed time period; setting a stop-loss distance in ticks is a different feature. Use an alert-compatible chart interval and test the resulting alert in your demo setup. Check TradingView’s current tick-interval limitations before configuring automation.
Can I automate TradingView watchlist alerts for Tradovate with PickMyTrade?
The documented watchlist setup uses Create Settings for each symbol. Save the symbol’s order parameters first, then generate an indicator alert with the TradingView Symbol field blank so PickMyTrade reads the ticker from the JSON. Copy the generated message and webhook URL into TradingView. Check every symbol’s saved settings before using the alert. Follow the watchlist setup guide for the full configuration.