I’m running a Make.com automation, and after processing a batch of ~300 calls yesterday, I noticed that for all calls with Ended Reason = customer-did-not-answer, no webhooks were fired. These calls do appear in the Call Logs (with Start Time = N/A), but no webhooks are triggered. A few weeks ago, this same situation (customer-did-not-answer, Start Time = N/A) was working correctly — webhooks were firing (status-updates) as expected. This is urgent, as our Make.com workflows are blocked until this is resolved. Example Call IDs (no webhook firing, October 8, 5:30–6:00 PM): - 0199c5d5-c06d-7996-a777-2bb59c884517 - 0199c5d5-bb12-7bb8-b858-b932627ab61f - 0199c5d3-599a-7881-a044-3324e64a2989 - 0199c5d2-99de-7110-ac25-89f7670a9a4e - 0199c5ce-fa0b-7ff0-b393-cf6fd3b997bf Example Call IDs (webhooks fired correctly, September 10): - 194e3b66-5193-4401-bdba-96e52d0395b2 - 8aa54171-237d-4027-a526-b2ea8bb5f2e9 - 8245ef30-e48b-475b-b339-42fc4bc73d8b - 7048b66b-0cfd-4e07-942f-b9e09282f787 - 1a2f37aa-2ea8-40ac-92b3-7c1d2a5effb7 Can someone help investigate and let me know how we can get webhook events firing again for these calls?

I can help you look into why the webhooks stopped firing for calls marked as “customer-did-not-answer.” It sounds like something might’ve changed in how those events are triggered. Do you know if there were any recent updates to your webhook setup or changes in the call event settings on your Make scenario? @Rob

Thank you @Vercel ! No changes at all — identical webhook setup on September 10 to October 8. One thesis I had was that enabling Voicemail Detection later on caused the issue (e.g. when Voicemail Detection wasn't enabled before, those that went to voicemail showed up as "customer-did-not-answer", which previously had webhooks firing). However, after I tested this by disabling Voicemail Detection and re-calling a "customer-did-not-answer" number where the webhook didn't fire — the same issue occurred (no webhook firing).

@User In your agent, if you scroll down to server messages, all options besides the one you want need to be turned off, probably some overriding issue or somethings not sure, but this fixed it for me

Got it, so it’s clear the issue isn’t from Voicemail Detection. I can help you trace what’s blocking those “customer-did-not-answer” calls from triggering webhooks. It could be linked to how the system now handles calls without a start time or how the event is being flagged before completion. Let’s take it privately so I can look through your webhook setup, logs, and event flow in detail to pinpoint the cause and get it working again. @Rob

@mm Thanks for the tip! I turned off all server messages except "end-of-call-report" and "status-update" which are the only two I need. After testing, it does look like now "end-of-call-report" is firing for "customer-did-not-answer" (this did not work before) – but for some reason "status-update" is still NOT firing. For all other endedreason statuses, both are correctly firing.

If the call times out, the status update will not be sent. Here is a log:

🔵 22:00:37:894 Call is already ended, skipping call status update.: 0199c5d2-99de-7110-ac25-89f7670a9a4e. Call end tried with: customer-did-not-answer

Thanks! Just to clarify: - For customer-did-not-answer — was it always the case that no status-update is sent if the call times out? Last month we saw those events fire, so has this behavior changed and will it remain this way? - Does end-of-call-report always fire for every call, regardless of endedReason or timeout?

It should fire for calls even if it times out. The call-status webhook should be working and was previously, but our team is currently working on resolving it