Can old and new TradingView alerts run at the same time and duplicate trades?
Yes. A newly created alert does not automatically remove the previous server-side alert. If both target the same execution route, both can independently fire and create duplicate commands.
What this means in practice
Yes. A newly created alert does not automatically remove the previous server-side alert. If both target the same execution route, both can independently fire and create duplicate commands. This page is specifically about “Can old and new TradingView alerts run at the same time and duplicate trades?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Old alert forgotten
Compare TradingView alert IDs, creation times and saved script versions. Two active server-side alerts can emit the same setup twice. Disable or isolate the obsolete alert and retest with only the intended route active. For Scenario A — Old alert forgotten on question 53, use that evidence specifically to answer “Can old and new TradingView alerts run at the same time and duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — Migration overlap
Compare TradingView alert IDs, creation times and saved script versions. Two active server-side alerts can emit the same setup twice. Disable or isolate the obsolete alert and retest with only the intended route active. For Scenario B — Migration overlap on question 53, use that evidence specifically to answer “Can old and new TradingView alerts run at the same time and duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Two browser-created alerts share same webhook
Inspect the mechanism named by “Scenario C — Two browser-created alerts share same webhook” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Two browser-created alerts share same webhook on question 53, use that evidence specifically to answer “Can old and new TradingView alerts run at the same time and duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- active server-side TradingView alert instance
- saved symbol, timeframe and inputs
- realtime versus confirmed-bar behavior
- exact message emitted by the active alert
Practical rule
For “Can old and new TradingView alerts run at the same time and duplicate trades?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.
Decision summary
Direct answer: Yes. A newly created alert does not automatically remove the previous server-side alert. If both target the same execution route, both can independently fire and create duplicate commands.
Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.