Retry or Queuing logic to handle events when the notification URL is unavailable
There are times where the application hosting the notificationURL for a listener event goes down. Today the event logic fires a message to the notificationURL and does not check that the system received the message. To avoid missing events, it would be great if there was a failsafe mechanism that takes advantage of retrying and/or queuing the events in the event that the notificationURL does not respond to events sent to it.

Due to the large number of historical requests, we are closing some suggested ideas so that we can focus on more recent and popular ones. This item was closed because it was over two years old and had less than 5 votes. If you still feel your idea is important and should be rereviewed please feel free to create a new UserVoice submission.
-
Ashish Kalve commented
Thank for you creating this user story. I think this feature will be great value to any organizations expecting guaranteed delivery of events generated within Condeco that are critical to drive all downstream functionalities in case if failure, downtime. Please help prioritize this if possible.