Store failed webhooks and add retry logic | Feature Requests

Store failed webhooks and add retry logic

Subsequent Clownfish

Users could benefit from an area to review failed webhooks and a way to retry failed webhooks. This will be more important as AI enables broader access to API functions.

Created by Jacques Reulet

Subsequent Clownfish

Sarah Hum, thanks for your reply. I think this post must have been created by one of your staff on the back of a support request (... I didn't create it).
The ability to see completed and failed webhooks (and filter based on status) is quite common. Sometimes there may be nothing in the server logs on the target system for the webhook. For example, if the webhook url is misconfigured (trival example) or if there is a gateway error or timeout before the request reaches the target system. Even if the target system is reached, on a busy server the server logs may not be easy to review.
In terms of retry, the system sending the webhook might back off exponentially and then give up after a certain number of retries. This can help if there is temporary downtime or a bug on the target system that needs fixing. Typical backoff sequence might be 1 minute, 1 hour, 12 hours, 3 days.
A very useful feature of some systems is the ability to manually resend a webhook after the max retries has been exceeded.

Sarah Hum

Great to hear your perspective, Subsequent Clownfish! Following up on this:

What specific information would you like to see in the review area for failed webhooks?
How frequently do you anticipate needing to retry failed webhooks?
Are there any specific conditions under which you would prefer the system to automatically retry a failed webhook?

Photo Viewer