Why does TradingView open duplicate trades?

What this means in practice

Duplicates can come from Pine logic, duplicate alerts, duplicate execution instances or retries. TradingView can resend certain 5xx webhooks three times, so one trigger can create up to four sends. This page is specifically about “Why does TradingView open duplicate trades?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Two alerts

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 — Two alerts on question 17, use that evidence specifically to answer “Why does TradingView open duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — freq_all

Inspect the TradingView alert log during the still-open candle. Realtime recalculation can make the condition true several times; add explicit intrabar state or a per-bar guard if the strategy intends only one logical action. For Scenario B — freq_all on question 17, use that evidence specifically to answer “Why does TradingView open duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Two cBots

Count authenticated cBot or connector sessions for the target account. One webhook handled by two execution instances can create two trades even when TradingView delivered a single request. For Scenario C — Two cBots on question 17, use that evidence specifically to answer “Why does TradingView open duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.

Scenario D — 500 after queue

Treat this as duplicate-delivery risk. If the first request was already persisted or queued before the error response, a resend must reuse the same signal ID and produce no second trading effect. For Scenario D — 500 after queue on question 17, use that evidence specifically to answer “Why does TradingView open duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.

Scenario E — Retry ambiguity

Treat this as duplicate-delivery risk. If the first request was already persisted or queued before the error response, a resend must reuse the same signal ID and produce no second trading effect. For Scenario E — Retry ambiguity on question 17, use that evidence specifically to answer “Why does TradingView open duplicate trades?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• intended signal/action
• last stage that definitely succeeded
• first stage that differs from intent
• final cTrader state after the event

Practical rule

For “Why does TradingView open 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.