-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CAL-3752] Unreliable Triggering and Payload Inconsistencies in Calcom Webhooks #15078
Comments
Hey @hussamkhatib, great to see you back! 😀 We definitely remember working through some challenges together. I'm diving into the details of what you've shared and will circle back with a comprehensive response soon. |
Additionally, the automated emails the calcom would send to all attendees and the organizer once the recording is completed, no longer get sent |
To address the issues you're encountering with Cal.com webhooks, let's dive into specifics:
For further assistance, please share more details about your Cal.com codebase version, the steps you're following to set up and trigger the webhooks, and any specific error messages or logs. This information will be vital for diagnosing and resolving the issues more effectively.
|
Our meeting ended and started trigger doesn't trigger at the exact time as we have a corn job running every 5 minute that then triggers all webhooks. Your meeting starts at 4:50 and ends at 4:51, that's why both were triggered at the same time at 4:54
That can happen when the trigger time is closer than 5 minutes to the current time. Also there was a current fix for another issue related to that #14864, however old bookings that were created before the fix can still cause the issue
We are currently working on fixing the request body of the meeting started and meeting ended trigger #15036
Tagging @Udit-takkar for this one @hussamkhatib Let me know if I didn't address everything and if you have any questions to that |
added highest priority |
Thanks @CarinaWolli, that’s helpful! |
This was fixed yesterday. |
We can’t figure out which PR you are referring to, mind linking it?
…On Fri, May 17, 2024 at 5:14 AM Udit Takkar ***@***.***> wrote:
RECORDING_READY
Does not trigger at all. (Note: It's been only few days since we are
facing this Issue, it used to work fine a few days back)
This was fixed yesterday.
—
Reply to this email directly, view it on GitHub
<#15078 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ4JMSPRB77FD5EOE6RDVTZCXJ6RAVCNFSM6AAAAABH2KLRFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJXGIZDKMZQGQ>
.
You are receiving this because you commented.Message ID: <calcom/cal.
***@***.***>
|
@l0g1x No PR was required for this. I had to make a POST request to restart subscribing to recording ready event. |
Thanks @Udit-takkar, It works now |
@Udit-takkar We had a Meeting an hour back, the recording ready din't trigger again. |
Restarted this again. investigating why it's failing sometimes |
Issue Summary
My team has been facing issues with calcom webhooks one after the other. The triggering of the webhooks isn't reliable, so is the payload of the triggers
MEETING_STARTED and MEETING_ENDED
Sometimes it does not trigger at all. (It might be the case when the booking is booked very close to the current time)
Irregular Request body (main issue)
organizer
Object.RECORDING_READY
Steps to Reproduce
Follow the steps mentioned in the docs to setup webhooks and print logs of the request body with timestamps
Use the link provided in the meeting(CAL video) and record the meeting
Actual Results
Evidence
CAL-3752
The text was updated successfully, but these errors were encountered: