News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Search
Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Webhook - Retry Support
Tags: webhooks
Nov 9, 2021 at 4:33am   •   2 replies  •  0 likes
Jorge Correia

From the documentation it seems that, by design, RingCentral webhooks do not support retrying and only sends the notifications once.

Its seems a poor design and will be very difficult to ensure that no notifications are lost. Even high availability environments in the cloud (Azure or AWS) do not ensure 100% availability.

Similar systems will try to publish the notifications a number of times, for a specific period time and only after that, the notification will be dropped and won't be delivered.

This feature is quite important for us when integrating with RingCentral. So I would like to know if a retrying mechanism for webhooks is something you are considering to implement in a future version of your software and if so when will that be available?


2 Answers
answered on Nov 9, 2021 at 11:24am  

Talking to the engineering team. RingCentral Webhooks does retry 3 attempts in a short period time before stopping sending notification to that channel.


 0
on Nov 10, 2021 at 8:30am   •  0 likes

Can you please give me more information about the 3 retries attempts? What is the time between retries? What happen after the failed 3 attempts? Is the subscription backlisted? Is there any reconciliation mechanism to automatically make a blacklisted subscription active again?

answered on Nov 9, 2021 at 12:26pm  

RingCentral notifications are used for "RealTime Call-Message-Status" tracking purposes. The apps that uses Subscriptions with RC rely on these notifications for certain use cases like UI interactions , real time call monitoring ,device status monitoring and message notifications.


From backend perspective , the notification subsystem retries upto 3 time with very short interval to deliver the notifications to subscribed endpoint and if the delivery fails , it will not resend stale notifications.


 0
on Nov 10, 2021 at 8:31am   •  0 likes

Can you please give me more information about the 3 retries attempts? What is the time between retries? What happen after the failed 3 attempts? Is the subscription backlisted? Is there any reconciliation mechanism to automatically make a blacklisted subscription active again?



A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

PRODUCTS
RingEX
Message
Video
Phone
OPEN ECOSYSTEM
Developer Platform
APIs
Integrated Apps
App Gallery
Developer support
Games and rewards

RESOURCES
Resource center
Blog
Product Releases
Accessibility
QUICK LINKS
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us