Does TradingView resend a webhook alert?
Sometimes, in some cases. TradingView documents an exact resubmission policy, and it's narrower than a lot of troubleshooting guides make it sound. Here's the real rule, what it means for an alert pointed at Autoview, and the one honest case where a resend could still happen.
TradingView's actual policy
Per TradingView's own webhook resubmission documentation: if the server receiving the webhook responds with an HTTP status code between 500 and 599, with the single exception of 504, TradingView resends the identical webhook after 5 seconds. It will do this up to 3 times, so one alert firing can produce as many as 4 total delivery attempts if every one of them comes back with a 500-599 status.
That's the whole policy. It doesn't cover timeouts on their own, it doesn't cover 4xx responses, and it explicitly carves out 504. A lot of troubleshooting content simplifies this to "TradingView doesn't retry," which is close but not accurate, or leaves the status-code detail out entirely. The 500-599 trigger is real and worth knowing if you're trying to reason about whether a resend could ever double up an order.
What Autoview actually sends back
Every response Autoview's webhook endpoint returns under normal operation falls into two buckets, and neither one is in TradingView's resend range:
- 200, when the request is accepted. Autoview returns this immediately on receipt, before it has placed any order on a connected exchange, so its own processing time never factors into whether TradingView considers the delivery slow.
- A 4xx rejection, when something about the request itself is wrong:
415for an unsupported content type,404for an unknown hook,401for a bad webhook key,411for an empty request body, or422when no exchange account is linked to the hook. Every one of these is a client-side rejection code, none of them 500 or above.
A normal rejection, of any kind Autoview's webhook logic produces on purpose, sits outside the 500-599 window. TradingView won't resend it, and Autoview won't see the same alert twice because of this mechanism.
The one real exception, stated plainly
This isn't a claim that a resend is impossible, just that it isn't caused by anything Autoview's own webhook logic does on purpose. If something fails before Autoview's code gets far enough to send one of the responses above, for example a backend outage severe enough that the database read behind hook validation fails outright, the hosting platform can return a generic server error in the 500-599 range on Autoview's behalf. That status would fall inside TradingView's resend window, and a resubmission could follow.
That's an infrastructure failure, not a routine rejection or a slow trade. It isn't something you can trigger by sending a malformed alert, hitting a rate limit, or having a trade take a while to fill. If you ever suspect this happened, the log is the place to check: two identical entries seconds apart, both otherwise looking normal, would be the signature.
If you're worried about the order itself, not just the alert
A resent webhook and a duplicate order are two different questions. This page is about whether TradingView sends the same alert twice. For what actually causes Autoview to place two orders from what looks like one signal, including the far more common causes (two senders both pointed at the same account, or a repainting indicator firing twice honestly), see duplicate or repeated orders. Its dedupe= parameter doesn't run on the cloud webhook platform, so it wouldn't catch a resend-driven repeat either, but that mechanism is not the one this page is about.