Updated .
Why a trading webhook fails, and where to look
A trading webhook fails when the receiver answers too slowly, uses a port or address the sender refuses, or returns an error the sender does not send again. TradingView's help pages, opened on 11 November 2026, give the receiver 3 seconds and accept only ports 80 and 443. Freqtrade's webhook page leaves retries off by default.
Did the alert fire, or did the delivery fail?
Start with the sender's own log. TradingView's setup page says webhooks may occasionally fail to reach the address you gave, and that the Webhook status column in the alert log shows each delivery. A row in that log means the alert fired. Its Webhook status is about the delivery.
Plan caps, alert schedules, and how long the log keeps a row are in TradingView, exchange alerts, and a dedicated alert app.
Freqtrade sends webhooks the other way: the bot posts a message when, for example, it places an order or that order fills. On 27 May 2024 a Freqtrade user reported a Discord webhook that sent no message, with no error and no webhook line in the log. A project member replied that no message goes out unless an entry or an exit fills, and that silence most likely means a wrong webhook address or a message expected at the wrong moment. A second reply said the indentation had moved the Discord block into the Telegram section of the config file.
A bot that does not trade sends nothing. Freqtrade's FAQ says that after an "Outdated history" warning the bot does not enter a trade for that pair. A wrong system time is one of the causes it lists. The FAQ also says the --logfile option writes a copy of the log to a file.
What limits does TradingView put on a webhook?
TradingView's help pages list these:
- Account. Webhook alerts are allowed only when 2-factor authentication is on.
- Port. Only ports 80 and 443 are accepted.
- Address. The error page lists localhost, an internal IP, and a name that resolves to a private address as not allowed. The port page says IPv6 is not working with webhooks at the moment.
- Encryption. A secure-connection error means the server answered without encryption, or the connection could not be secured. The listed cause is incorrect TLS settings.
- Body. Valid JSON goes out as
application/json, and any other message astext/plain. The error page lists an invalid body format among the causes of a client error, a status from 400 to 499. - Firewall. The setup page lists four addresses TradingView sends from: 52.89.214.238, 34.212.75.30, 54.218.53.128, and 52.32.178.7. A firewall that leaves one out can drop a request before the bot sees it.
Why a slow answer loses the alert
The error page says a timeout means the receiving server did not respond within 3 seconds, and lists an overloaded server and network issues as causes. The setup page says a request that takes longer than that to process is cancelled. A receiver that does slow work before it answers, such as calling an exchange, can cross that line.
Which failures are tried again?
| Sender | How long it waits | When it sends again |
|---|---|---|
| TradingView | 3 seconds, then the request is cancelled | After a status from 500 to 599, except 504, it sends again 5 seconds later, up to 3 times. That is 4 sends at most |
| Freqtrade | 10 seconds, or the timeout you set | Not by default: retries is 0, which is disabled. Above 0, retry_delay sets the pause, 0.1 seconds by default |
TradingView's resubmission page describes a resend only for those server errors. It names none for a timeout, a redirect, a client error, or status 504. The resend can also repeat work: a receiver that acts on the message and then answers 500 can get the same trigger four times.
Freqtrade's page notes that more retries may slow the bot down when the webhook has connectivity issues. The sender code on its stable branch, read the same day, logs a warning that starts with Could not call webhook url when a send fails.
Habits that make a miss visible
- Answer first, then do the slow work. The answer has to arrive inside the sender's wait: 3 seconds for TradingView, the
timeoutsetting for Freqtrade. - Log every delivery with the time it arrived, so you can read your log next to the sender's.
- Keep a record of what you have handled. A trigger sent four times is then acted on once.
A feed with a cursor, for what a webhook missed
On this site, the events feed lists the alerts your own rules fired. Software reads it with an API key, and Plans lists a key on every plan. Each answer carries a next_cursor. Store it and send it back as cursor on the next request, and you read each alert once. The Freqtrade guide and the Hummingbot guide both read this feed.
The feed keeps alerts for 7 days. When gap is true, an alert after your cursor has aged out of the feed. Read the rule's record, or the alert by its id, and drop duplicates by id. An alert waiting for quiet hours or the daily limit is still in the feed. Alerts from a muted rule are not.
On 11 November 2026, Plans listed signed webhooks to your own server as built and not yet open to all accounts. The webhook page describes a receiver's checks: reject a signature whose time is more than 300 seconds from your clock, drop an event id you have already handled, and read the feed from the stored cursor when a sequence number is skipped.
Terminal gives every plan an API key, and its events feed returns each alert once when you store the cursor and send it back. It is not investment advice.
FAQ
Why did my TradingView webhook not reach my bot?
TradingView's help pages say a request is cancelled when the receiver takes longer than 3 seconds, that only ports 80 and 443 are accepted, and that webhook alerts need 2-factor authentication. They describe a resend only after a status from 500 to 599, except 504. The Webhook status column in the alert log shows each delivery.
Why did the same alert arrive more than once?
TradingView sends a webhook again after a status from 500 to 599, except 504. Each resend comes 5 seconds later, with up to 3 resends, so one trigger can arrive 4 times. Freqtrade tries a failed call again only when its retries setting is above 0.
What can a bot read when a webhook is not an option?
On this site, every plan includes an API key, and the events feed lists your alerts. Store the cursor from each answer, send it on the next request, and you read each alert once. On 11 November 2026, Plans listed signed webhooks as built and not yet open to all accounts.
Sources
Opened 2026-11-11 unless a page prints its own date.
- TradingView, webhook errors: timeout, client errors, TLS, private addresses.
- TradingView, webhook setup: cancelled requests, 2-factor authentication, content type, addresses, Webhook status.
- TradingView, resubmission: 500 to 599 except 504, 4 sends.
- TradingView, port numbers: ports, IPv6.
- Freqtrade, webhook usage: when a message is sent, retries, delay, timeout.
- Freqtrade, sender code, stable branch: the warning logged when a send fails.
- Freqtrade, FAQ: system time,
--logfile. - Freqtrade, Discord report, 27 May 2024: no message, misplaced block.
- Plans: key on every plan; signed webhooks built, not yet open to all accounts.
- Events: cursor, 7-day feed,
gap. - Webhooks: 300-second signature check, repeated ids, sequence gap.