Webhook delivery drops under load
Power users report missed and duplicated webhook events during traffic spikes, forcing them to build their own reconciliation.
Priority score
88/100
Affected users
38
Mentions
61
Urgency
★★★★★
AI recommended action
Add delivery guarantees (at-least-once + idempotency keys) and a replay endpoint. Concentrated among your highest-MRR accounts — churn risk is disproportionate to the ticket count.
Sentiment breakdown
6% positive21% neutral73% negative
What customers actually said (3)
- eng@scalrZendesk2026-05-27
“We dropped ~3% of webhook events during our launch spike. Had to build a polling fallback, which defeats the point.”
- Tomas L.Intercom2026-05-26
“Got the same event delivered twice and it double-charged in our system. Please add idempotency keys.”
- @buildwithanaTwitter2026-05-23
“Is there a webhook replay endpoint? Cannot find it in the docs.”