I have a complex Make.com setup that drives outbound calls through VAPI. The flow goes down a Lead List and triggers calls via API. Post-call events are sent to my webhook. For some calls (minority of total), I’m receiving an additional message.type = status-update with status = ended that references a different Call ID than the one I triggered. These “extra” calls have no corresponding log of a call being initiated from my scenario, and critically, they lack customer name and External ID fields. This makes me believe VAPI may be automatically recalling numbers. Examples (all times reference when the call ends): - Correct Call: 2025-09-09 09:15:44 → Call ID 7932aaad-8cc1-48bb-bd6f-a2b5a2063423 - Incorrect Call: 2025-09-09 09:24:47 → Call ID 1faac863-8c88-4574-a63e-5ef455ab7d8b - Correct Call: 2025-09-09 15:36:27 → Call ID 9351e5fc-e685-477f-88a8-cc728edf0ccb - Incorrect Call: 2025-09-09 15:49:54 → Call ID af6868ed-ad62-4ac3-bc2b-705e55038fb6 - Correct Call: 2025-09-09 09:20:00 → Call ID 339d8c47-6038-4eaa-a938-ec010f79a6ec - Incorrect Call: 2025-09-09 09:26:25 → Call ID dd7268e2-9715-4e68-a4fd-bd9b72d6e603 - Correct Call: 2025-09-09 15:37:34 → Call ID 96613386-1b46-4e87-a08d-75cc5774cf6e - Incorrect Call: 2025-09-09 15:53:45 → Call ID e0e646a2-1611-4b87-85e4-853bb0e8a5b5 - Correct Call: 2025-09-09 16:23:50 → Call ID 151108e1-b9dd-4ee4-a2b1-699604d4478d - Incorrect Call: 2025-09-09 16:30:51 → Call ID 49d66991-93aa-4de6-92fa-467466102c26 Pattern observed: - The “incorrect” calls occur minutes after a valid call. - They do not have customer name or External ID values (always present in my triggered calls). - They appear only as status-update → ended events in my webhook; there is no trigger. Can someone please explain why this is happening? Thank you!

Hello, Can you try a few potential troubleshooting steps?: 1. First, verify that your [Make.com](http://Make.com) scenario isn't accidentally triggering multiple calls (e.g., through duplicate webhook triggers or retry logic) 2. You can monitor the exact call flow by checking: - The original Call ID from your [Make.com](http://Make.com) trigger - The corresponding status updates for that specific Call ID - The timestamp and sequence of events for both the original and "extra" calls 3. Since these extra calls lack customer name and External ID fields, this suggests they weren't created through your normal [Make.com](http://Make.com) flow. I recommend: 1. Logging all Call IDs and their associated events 2. Adding distinctive External IDs to your calls to track their origin 3. Checking if there are any automatic retry configurations in your [Make.com](http://Make.com) scenario If this doesn’t resolve the issue, please let us know and we’ll be happy to step in and assist further.