Hi everyone, I’m working with VAPI and Make.com, and I’m encountering an issue where the webhook I’ve set up is being triggered multiple times without additional requests being made, it’s returning the same data over and over… Here’s the situation: I’ve set up a webhook in Make.com to handle VAPI requests. ( vapi ServerUrl ) The webhook is supposed to trigger only once per request, but it’s firing multiple times for a single request, causing duplicate executions in my scenario. I’ve double-checked the setup on both VAPI and Make.com sides, and I can’t figure out why this is happening. Has anyone else experienced this issue? How can I ensure that the webhook only triggers once per request? Any advice or troubleshooting tips would be greatly appreciated! https://cdn.discordapp.com/attachments/1285783027128995860/1285783027401883709/problem.PNG?ex=66eb8642&is=66ea34c2&hm=7a57e4fce6d9ced2c150cf21c6df55192758e3513358065042342202d34e6d28& https://cdn.discordapp.com/attachments/1285783027128995860/1285783028064321546/recieve_call.PNG?ex=66eb8642&is=66ea34c2&hm=5675aeebe6a246ae0b83f490f26a38e17303339e46a320ccc6782a1e285d3681& https://cdn.discordapp.com/attachments/1285783027128995860/1285783028278366330/vapi_serverurl.PNG?ex=66eb8642&is=66ea34c2&hm=210b12406ebc34605435a2ae5879b4dff751669d8251219021ea24b9bd37b617&

@zehaan Hello! It sounds like you're experiencing a common issue where webhooks can sometimes trigger multiple times for a single event. This can happen due to various reasons such as network glitches, retries from the sending service, or issues with the receiving endpoint. Here are some troubleshooting tips to help you ensure that your webhook only triggers once per request: 1. Check for Retries: Make sure that VAPI isn't configured to retry sending the webhook in case of failure or slow responses. If it is, adjust the retry settings to prevent multiple triggers. 2. Idempotency: Implement an idempotency check in your Make.com scenario. Store the unique identifiers of processed requests and check against this before processing new ones to prevent duplicates. 3. Response Time: Ensure that your webhook endpoint on Make.com is responding quickly enough. If the response is too slow, VAPI might consider it a timeout and retry. 4. Status Codes: Verify that your Make.com webhook is returning the correct HTTP status codes. A 200 OK status code should be returned to acknowledge successful receipt of the webhook without any issues. 5. Logs and Monitoring: Review the logs on both VAPI and Make.com to see if there are multiple requests being sent or if it's an issue with the scenario on Make.com. 6. Deduplication Logic: Add logic within your Make.com scenario to deduplicate events based on a unique attribute in the data payload. 7. Contact Support: If you've gone through these steps and the issue persists, it might be helpful to contact support for both VAPI and Make.com for further assistance. If you need further assistance or have any more questions, feel free to ask. If your issue is resolved, let me know, and I can close this support ticket for you.

i don't get the term retries... How to check for retries

@zehaan Certainly! The term "retries" refers to the mechanism where a service will attempt to resend a webhook notification if the initial attempt fails or doesn't receive a timely acknowledgment. This can happen if the receiving server doesn't respond quickly enough, or if there's an error in processing the request, leading the sending service to believe that the message wasn't delivered successfully. To check for retries, you would typically: 1. Review Documentation: Look at the VAPI documentation to understand how webhook retries are handled. There might be information on how to configure or disable retries. 2. Check Configuration: In your VAPI dashboard or settings, there may be options to configure the retry policy for webhooks. You can adjust these settings to reduce or eliminate retries. 3. Examine Logs: Check the logs in both VAPI and Make.com for entries that indicate multiple attempts to deliver the same webhook. This can confirm if retries are occurring. 4. Response Codes: Ensure that your webhook endpoint is returning the correct HTTP response codes. A successful delivery should always return a 200 OK response to prevent retries. 5. Contact Support: If you're unsure about how to check or configure retries in VAPI, you may need to reach out to VAPI's support team for guidance. If you need assistance with reviewing your VAPI settings or if you have any other questions, please let me know. If you're ready to close this support ticket, just give me a confirmation.

no there is nothing like that in vapi

share call id.

Marking it as close since there was no response.