Webhooks Not Firing for “customer-did-not-answer” Calls
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):
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
- 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
