Webhooks are a powerful way to keep your systems in sync. But not all events are created equal. High-frequency triggers like presence or typing indicators can overwhelm your servers during outages, while critical events like message delivery need guaranteed reliability. That’s why we’re giving you more control.
What we're launching
Granular webhook retry control. You can now choose which webhook events should auto-retry on failure and which shouldn't, instead of applying retry logic to all webhooks universally with CometChat
Why this matters for developers
Most platforms auto-retry every webhook event when your server returns an error. Sounds helpful until high-frequency events like user online/offline or call started start flooding your servers during outages.
You need retries for critical events like message received, but not for noisy presence updates that fire constantly. This gives you that control.
Key features
Per-event retry configuration
Enable retries only for webhooks that matter
High-frequency event protection
Skip retries for presence updates, typing indicators, and other noisy events
Critical event reliability
Ensure important webhooks like message delivery get retried
Server load management
Prevent webhook floods during outages or server issues
Tech behind this
Traditional webhook systems apply retry logic globally all events get the same treatment. We built event-specific retry queues that respect your configuration per webhook type, preventing cascade failures while maintaining reliability for business-critical events.
How to get started
Available now in your CometChat dashboard under Webhooks settings. Select which event types should retry on failure. Recommended: enable for message events, disable for presence and typing events.
Nivedita Bharathy
Product Marketing Specialist , CometChat