Webhooks stategy explained

[williamzeni99]

Hi everybody!

I have self-hosted the docker image and it works smoothly. I tried to add a webhook to one event and It actually runs, but it seems to run even if it shouldn't. If I raise an error 500 in my webhook script, should calcom drop the booking process? What is the policy of failed webhooks? Does it ignore the script errors?

[dosubot[bot]]

Hey there, @williamzeni99! 👋 I'm here to assist you with bugs, questions, or if you want to become a contributor. Just ask!

I found two similar closed issues related to webhooks in Cal.com:

1. [CAL-2714]: This issue discusses session booking events going through the webhook even when there is a credit card payment failure. No solution was found in the comments. View issue ^[1].

2. [CAL-416]: This issue involves bookings bypassing required confirmation and workflows/webhooks not firing. No solution was found in the comments. View issue ^[2].

Regarding your question, Cal.com does have a mechanism to prevent the booking process from completing if a webhook returns an error. The error handling is integrated into the booking process, and if an error occurs, such as a missing event data or invalid duration, the process is halted, and an error message is displayed to the user ^[3][4].

Additionally, Cal.com determines whether to retry a failed webhook or proceed with the booking process by using a try-catch mechanism. If an error is intended to trigger a retry, it must be thrown as a RetryableError ^[5].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[williamzeni99]

@dosu If there exist the mechanism to stop the process of booking if a webhook fails, how can I implement it? I set up the webook in my cal.com and I have enabled a redirect page. I have a nuxt app api exposed just for raising 500 or 400 errors but still I can complete the booking process with a successful state.

[dosubot[bot]]

Cal.com handles webhook error responses by logging errors but does not automatically halt the booking process when a webhook returns a 500 or 400 error. The default behavior is to log the error details, including the event trigger, subscriber URL, booking ID, and booking UID, without stopping the booking process ^[1].

To implement a mechanism that stops the booking process when a webhook fails, you would need to customize the code to handle specific error responses and decide whether to halt the process based on those errors. This might involve modifying the webhook handling logic to check for certain error codes and then programmatically prevent the booking from completing.

If you have a redirect page set up, you might also need to ensure that the logic for handling errors and redirects is correctly implemented to reflect the desired behavior when a webhook error occurs.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}