Does TradingView retry webhooks?
Short answer: TradingView documents one resend case: if your server returns HTTP 500–599 (except 504), it sends the webhook again after 5 seconds, with a total of 3 such resends, so at most 4 sends per trigger (webhook resubmission). A request that takes longer than about 3 seconds is cancelled (TradingView: webhooks).
What gets resent and what doesn't
| Your server… | TradingView |
|---|---|
| Answers 2xx within 3 s | Delivered |
| Returns 500–599 (not 504) | Resent after 5 s, max 3 resends |
| Returns 504 | Not resent |
| Takes longer than 3 s | Cancelled |
| Is down / unreachable | Webhook fails; check the alert log |
Watch out for duplicates
Because a 5xx can trigger a total of 3 such resends, an app that processed the alert and then crashed before replying can receive the same alert again. Make your endpoint ignore repeats, for example by putting {{timenow}} (the alert's fire time, TradingView: placeholders) in the message and dropping ones it has already seen. See duplicate TradingView alerts.
Where HoldAlarms fits
HoldAlarms answers TradingView itself, so TradingView's resend rules stop mattering for your endpoint. HoldAlarms retries up to 5 times. Retries finish within about 3 minutes, or up to about 6 with Retry-After. Retries cover failures such as timeouts and 5xx replies. Permanent errors (400, 401, 403, 410, 413, 414, 415) aren't retried. Your endpoint gets 10 seconds per attempt. After that the alert is parked in a dead-letter queue, and failure emails are grouped and capped at up to 10 a day. Identical alerts from the same account within 20 seconds are forwarded once.
It adds a hop, and a delivered alert means your endpoint accepted it, not that your app finished processing it. Starter is €19/mo and Ops €49/mo.
Questions
Does TradingView retry failed webhooks?
TradingView documents one resend case: if your server returns HTTP 500–599 (except 504), it sends the webhook again after 5 seconds, with a total of 3 such resends.
What happens on a timeout?
A request that takes longer than about 3 seconds is cancelled.
How many times can one alert be sent?
At most 4: the first send plus 3 resends.
Does HoldAlarms retry timeouts?
Yes. HoldAlarms retries failed deliveries to your endpoint, including timeouts, network errors and 5xx replies, up to 5 times, 2 to 60 seconds apart. Retries finish within about 3 minutes, or up to about 6 with Retry-After. A reply of 400, 401, 403, 410, 413, 414 or 415 is a permanent error: it goes straight to the dead-letter queue. After the last retry, HoldAlarms parks the alert in a dead-letter queue.
More guides
- Why didn't my TradingView alert fire?
- TradingView webhook timeout: why "request took too long" happens
- TradingView webhook not received: 7 things to check
- Duplicate TradingView webhook alerts: why they happen and how to dedupe them
- The TradingView webhook checklist
- TradingView → HoldAlarms → n8n: step-by-step
- TradingView → HoldAlarms → TradersPost: setup and limits
- TradingView → HoldAlarms → PineConnector: setup
- TradingView → HoldAlarms → SignalStack: setup
- TradingView → HoldAlarms → PickMyTrade: setup
- TradingView → HoldAlarms → CrossTrade: setup and limits
- TradingView → HoldAlarms → Alerio: setup
- All guides
- All HoldAlarms questions
HoldAlarms is not affiliated with TradingView. TradingView is a trademark of TradingView, Inc.