Webhook 429 Too Many Requests: fix provider throttling
Webhook providers enforce per-endpoint and per-account rate limits. Bursts of 2xx failures, slow responses, or replay storms can push you into 429 even when traffic looks normal. Treat 429 as a flow-control signal: back off, respect Retry-After, and reduce concurrency.
Common causes
- Burst deliveries after deploy or queue drain.
- Same endpoint shared by many subscriptions.
- Ignoring provider concurrency guidance.
How to fix
- Use 429 Detector and Rate Limit Tester to reproduce limits.
- Implement exponential backoff with jitter.
- Shard workloads or stagger subscriptions.
Use our tool
Open 429 DetectorRelated