Why did one TradingView trigger produce up to four webhook requests?

What this means in practice

TradingView can resend webhook requests that receive HTTP 500–599 except 504 after five seconds, up to three resends. One trigger can therefore produce at most four sends. This page is specifically about “Why did one TradingView trigger produce up to four webhook requests?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — 500 after already queueing

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 A — 500 after already queueing on question 34, use that evidence specifically to answer “Why did one TradingView trigger produce up to four webhook requests?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Temporary 503

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 B — Temporary 503 on question 34, use that evidence specifically to answer “Why did one TradingView trigger produce up to four webhook requests?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — 504 behaves differently

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 C — 504 behaves differently on question 34, use that evidence specifically to answer “Why did one TradingView trigger produce up to four webhook requests?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• TradingView alert log and exact send time
• HTTP status and receiver timestamp
• validated payload plus signal ID
• cTrader result only after transport is proven

Practical rule

For “Why did one TradingView trigger produce up to four webhook requests?”, 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.