HoldAlarms

Holds webhook alerts and retries delivery, with a dead-letter queue. Works with @tradingview @TrendSpider MetaTrader NinjaTrader cTrader n8n Make + any webhook.

[HoldAlarms @HoldAlarms]

HoldAlarms now works with @TrendSpider alerts. Paste your HoldAlarms URL as the webhook: we hold each alert, retry delivery if your bot is slow or down, and email you if one still fails.

[HoldAlarms @HoldAlarms]

@_kekule15 assume every webhook arrives twice.

[HoldAlarms @HoldAlarms]

@Desaa324 Out-of-order delivery. Send the update before the create and see what your handler does.

[HoldAlarms @HoldAlarms]

@popspinedev the tunnel one is sneaky. a test copy you forgot about still has the url. dedupe in one shared store, keyed on something in the alert body itself.

[HoldAlarms @HoldAlarms]

@LeadPulseHQ the webhook-started ones switching off on the first error is the nasty bit. one failed run and the scenario's just off.

[HoldAlarms @HoldAlarms]

Here you can find the docs for Make: https://t.co/sSg2OW6DvJ

[HoldAlarms @HoldAlarms]

If your endpoint is down when a Make scenario fires, the HTTP step fails and your endpoint never gets that alert.

Point the "Make a request" module at HoldAlarms instead: we answer Make once the alert is queued, then retry delivery to your endpoint. Still failing? Dead-letter queue and an email.

[HoldAlarms @HoldAlarms]

TrendSpider's docs say webhooks time out after five seconds, and their docs don't mention a resend.
TradingView cancels the request if your server takes longer than three seconds.

HoldAlarms answers, queues and retries for both. Retries finish within about 3 minutes, or up to about 6 if your server asks for longer waits with Retry-After.

https://t.co/04K7nYQ4hA

[HoldAlarms @HoldAlarms]

@hpmakwana Unknown is the right word. Most double charges start with someone treating it as failed and pressing retry.

[HoldAlarms @HoldAlarms]

@viveksharma2027 @Stringcodes cheapest line on the list until it isn't.

[HoldAlarms @HoldAlarms]

@_devdeep Unique constraint on the provider's event id. Insert it first; if the insert fails, return 200 and stop. The charge call then gets its own idempotency key.

[HoldAlarms @HoldAlarms]

@jainprayush9 the stuck spinner strikes again.

[HoldAlarms @HoldAlarms]

@selmakuno @cTrader append, then ack. always.

[HoldAlarms @HoldAlarms]

cTrader (@cTrader) cBots can now send alerts through HoldAlarms. Our free cBot posts each alert as JSON with cTrader's Http API, and HoldAlarms holds it and retries delivery to your endpoint. One catch: cTrader Cloud blocks web requests, so run it in Desktop or the CLI.

[HoldAlarms @HoldAlarms]

@MikeLopez Fair catch. Cancel, rejoin, cancel would collapse into one. If the provider sends an event id or sequence number, key on that and check current state before applying.

[HoldAlarms @HoldAlarms]

@KDope958 @POSTURE_CYBER @kayautomate make sure the form hits the production url, not /webhook-test/. the test one only listens while you click execute.

[HoldAlarms @HoldAlarms]

@n8n_io Here you can find the docs for @n8n_io: https://t.co/EqeFw5YM42

[HoldAlarms @HoldAlarms]

n8n (@n8n_io) workflows can send alerts through HoldAlarms: an HTTP Request node posts to your HoldAlarms URL, we queue it, deliver it to your endpoint and retry if it fails. Alerts that still fail land in a dead-letter queue.

[HoldAlarms @HoldAlarms]

@nasersadrmanesh a must-not check in the eval. love it.

[HoldAlarms @HoldAlarms]

@selmakuno @cTrader local forwarder works too.

[HoldAlarms @HoldAlarms]

Running your bot on port 5000 or 8080? TradingView only sends webhooks to ports 80 and 443, and doesn't support IPv6 for them. Requests to any other port are rejected. Put it behind a reverse proxy on 443 first.