Docs › Retries & failed alerts
Retries & failed alerts
If your endpoint doesn't accept an alert, HoldAlarms retries up to 5 times, 2 to 60 seconds apart. If it still fails, the alert is parked in the dead-letter queue and you get an email.
What counts as delivered
Each attempt waits up to 10 seconds. Any 2xx reply counts as accepted. Any other status, a redirect, a network error or a timeout is a failure. A delivered alert means your endpoint accepted it, not that your app finished processing it.
Retry schedule
- Up to 5 retries after the first attempt (6 attempts at most), 2 to 60 seconds apart.
- If your endpoint sends Retry-After, each wait can be longer, up to 60 seconds.
- Retries finish within about 3 minutes, or up to about 6 if your server asks for longer waits with Retry-After.
- Each destination has its own retries and dead-letter queue.
- Every attempt carries an
X-HookWatch-Attemptheader (1 for the first) and the sameIdempotency-Key, so your endpoint can spot a repeat.
Permanent errors
A reply of 400, 401, 403, 410, 413, 414 or 415 is a permanent error. It is not retried and goes straight to the dead-letter queue.
The dead-letter queue
Alerts that still fail after the last retry, or hit a permanent error, are parked in the dead-letter queue. The dashboard shows each recent alert's status, the number of attempts and the HTTP status. You get an email; failure emails are grouped and capped at up to 10 a day. There is no dashboard page to export or send these alerts again yourself: email support@holdalarms.com and we'll look at it with you.
How TradingView resends
This is TradingView's behavior, not ours, and TradingView may change it. According to TradingView's help pages, it cancels a webhook request that takes longer than about 3 seconds (TradingView: webhooks). If your server returns HTTP 500–599 except 504, it sends the webhook again after 5 seconds, with a total of 3 such resends (TradingView: webhook resubmission).
With HoldAlarms in between, TradingView talks to HoldAlarms, which answers as soon as the alert is queued; the retries to your endpoint are HoldAlarms' own, as described above.
← Zapier, Make, n8n, Grafana · API →
HoldAlarms is not affiliated with TradingView. TradingView is a trademark of TradingView, Inc.