What counts as an alert?
Each webhook TradingView sends to your HoldAlarms URL counts as one alert. Retries don't count, and an alert sent to several destinations still counts once. The free trial covers your first 300 alerts (or 7 days, whichever comes first).
Can one alert go to several endpoints?
Yes. Add up to 3 destinations on Starter or 15 on Ops; the free trial has 1. Every alert is delivered to each active destination separately, with its own retries and dead-letter queue, so one slow or broken endpoint doesn't hold up the others.
What happens to an alert my endpoint never accepts?
We retry up to 5 times, 2 to 60 seconds apart; permanent errors (400, 401, 403, 410, 413, 414, 415) aren't retried. Retries finish within about 3 minutes, or up to about 6 with Retry-After. If it still fails, the alert goes to the dead-letter queue, you get an email (failure emails are grouped and capped at up to 10 a day), and the dashboard shows each recent alert's status; support can look at it with you.
What happens when my trial ends?
Forwarding pauses and HoldAlarms doesn't forward the alert: when the 7 days are over it answers TradingView with HTTP 402 (payment required), and once the 300 free alerts are used it answers HTTP 403. Pick a plan to resume. You're never charged without choosing one.
Can I cancel anytime?
Yes. Cancel by email to support@holdalarms.com or with the “Verträge hier kündigen” (German for “cancel a contract here”) button at any time. Your plan stays active until the end of the period you've already paid for, and you won't be charged again.
Can I get a refund?
Yes: a full refund of your first payment if you ask within 14 days of it (once per person or organisation; your paid access then ends). Consumers also have a 14-day right of withdrawal. See Refunds & withdrawal.
Can I change plans?
For now, plan changes go through support: email support@holdalarms.com from your account email and we'll switch your plan.
What is receive lag?
The time between an alert firing in TradingView and HoldAlarms receiving it. Add "fired_at": "{{timenow}}" to your alert message and the dashboard shows the lag for each alert, plus the median (p50) and p95 over your last 100 alerts that include it. If the field is missing or isn't a time we can read (TradingView's {{timenow}}, an ISO 8601 time with Z or an offset like +02:00 or +0200, or a Unix timestamp), we simply show no lag; the alert is still forwarded as usual. Times without an offset are ignored because they're ambiguous, and so are times before 2020 or more than 7 days old. Use {{timenow}} (when the alert fired), not {{time}} (when the bar opened). Differences of up to 5 seconds between TradingView's clock and ours show as 0s.
What happens to a stale alert?
On paid plans (Starter and Ops) you can turn on a stale rule (off by default): "hold alerts older than" 30 seconds up to 30 minutes. An alert that arrives later than that after firing is parked in the dead-letter queue marked stale and is not forwarded to any of your destinations, so a late alert can't reach your endpoint. It still counts as a received alert, once, like any other alert, and the dashboard shows why it was held. Alerts without a readable fired_at are never held. Email support and we'll look at it with you. The free trial shows lag but can't use the stale rule.
How do I know TradingView is still sending?
Set up a heartbeat: a TradingView alert on a fixed schedule (every 1, 5 or 15 minutes) that posts to your heartbeat URL. If no beat arrives within the interval plus 60 seconds, we email you once, and again when beats resume. A heartbeat tells you that the scheduled alert stopped arriving, for example because it expired or was stopped in TradingView or TradingView isn't sending. It can't tell you about a single trade alert that wasn't sent. If you pause a heartbeat, no emails are sent.
Does a delivered alert mean the receiving app acted on it?
No. HoldAlarms confirms your destination accepted the alert (a 2xx reply). What happens next is up to the app that receives it. HoldAlarms delivers your alerts; it doesn't generate trading signals or place orders.
Do I still need my current webhook endpoint?
Yes. HoldAlarms sits between TradingView and the endpoint you already use (your own app or server, a third-party webhook service, a Discord or Telegram relay) and makes sure the alert reaches it.