Changed your strategy settings? Recreate the strategy alert to apply those changes to your automation. TradingView keeps a separate copy of the strategy when you create an alert. Editing the chart doesn’t refresh that copy. The chart can use your revised settings while the running alert keeps sending signals from the earlier version. For traders
Your TradingView strategy shows a winning trade. The alert arrived at a different time, and your broker recorded a different entry price. Before changing the strategy, find out which part of the trade actually changed. The TradingView backtest vs live difference comes from comparing a historical simulation with a real execution process. A backtest models
Duplicate TradingView orders show up as two entries in your alert log where one should be. Your broker shows a doubled position. The strategy crossed once, yet TradingView fired two webhooks and your account is now carrying twice the risk you intended. Duplicate TradingView orders almost always trace back to one of five Pine Script
Check your paid-indicator purchase, prepare questions for the author and review your alerts with this source-linked guide to TradingView Marketplace rules.
Multiple take profit levels automation looks like a settings problem. You pick three targets, split the contracts, paste one JSON into TradingView and you’re done. Then your strategy’s own exit fires on a Tuesday afternoon, and the account that should be flat is short five contracts. Nothing malfunctioned: the alert did exactly what its flags
You’ve got two indicators you trust. One spots the setup, the other confirms it, and you only want an order when both agree. Then you try to combine indicators in TradingView and hit the real snag. They’re separate scripts. One of them might be an invite-only tool whose code you’ll never see. Until October 2025,
{{strategy.market_position}} and {{strategy.market_position_size}} sit side by side among TradingView’s 11 strategy placeholders, and they look like two answers to the same question. They aren’t. The first sends a word: long, short or flat. The second sends a number, the absolute size of the position. Both describe the strategy after the order has filled, which is
Neither one does. That’s the honest answer, and most comparisons bury it under a feature table. TrendSpider’s Strategy Bots don’t place orders. They fire a webhook at SignalStack, which places the order. TradingView’s alerts don’t place orders either. They fire a webhook at whatever bridge you’ve pointed them at. So the platform question is settled
TradingView alert placeholders are the double-curly-brace tokens, such as {{close}}, that TradingView replaces with live values the moment an alert fires. Every strategy alert starts life as a template full of them. When an order fills, TradingView swaps each token for its value and posts the result to your webhook. Get one token wrong and
Your alert log shows a green checkmark. Your chart shows the entry. Your account shows nothing. That gap is the most common support ticket in retail trading automation, and almost nobody diagnoses it correctly the first time. Traders assume the alert broke. But in our queue, the alert is the culprit less than a third
