Structured data suddenly unavailable
# support
m
Hi - for some reason my assistant is no longer sending any structured data with its end of call report. Please can you help me fix this!
v
Thanks for reaching out! To help you further, could you please confirm if there have been any recent changes to your assistant's analysis plan, especially the
structuredDataPrompt
or
structuredDataSchema
settings? This will help identify if a configuration update might be causing the issue. For reference, structured data extraction relies on these settings in your assistant's configuration. You can review or update them as described in the [Vapi call analysis documentation](https://docs.vapi.ai/assistants/call-analysis). Source: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis)
m
No, I didn't change the analysis plan
The call summaries are still coming through fine as well
k
Hey Mike, Thanks for bringing this to our attention. The team is working on it and will fix it by the end of the day. In the meantime, use the API to update your assistant's analysis plan. The dashboard update overrides the plan, causing this issue. Let me know if you need further help.
m
What would I need to update?
I will also need to make more updates to the system prompt during the day today so if that overrides the plan then will updating via API be futile for now?
Can you direct me to the API docs for this?
I can't find them anywhere!
Sorry if that's painfully obvious for you but I can't see them for some reason
This is pretty urgent as I have an assistant being used by a client right now that is currently not working as a result of this bug
k
could you share: - The disrupted call ID This would really help us figure out what went wrong!
m
For this assistant: e6376e06-0935-45bb-91ba-e555e58ef769 The structured data flowed through for all calls up until the call ID: 2c9610db-ce05-4e92-b425-904198c1106e All subsequent calls have not sent structured data in the server message at the end of the call
I've updated it via the API now
I can see settings in the dashboard again now, however it still does not seem to be flowing through correctly in the end of call reports
Is this a problem on VAPI's end or something I can still resolve? My client has already noticed that things are not working correctly and updating via API has not resolved the problem. Please can you advise
s
Hey @mike we have resolved the issue. Can you share the call_id for which its not working.
t
i lost all my structured data
m
1141c64c-a1b4-47f5-8424-ce0899d7ee47
No structured data available from this call
I just made 2 test calls and they are not even appearing in my call logs
With no end of call report sent either
From my end unfortunately the problem has now gotten worse
n
@Shubham Bajaj this is an id for a call i am not getting the structured data ca61c65c-7733-4f94-8e14-7cf075aa0ebe. I updated the prompt analysis via web but it seems is not getting the structuredDataPrompt parameter
m
It seems this is an ongoing problem on VAPI's end
t
samething ,this is the call id d99681a3-f54f-49c9-9981-2e00276d79aa
v
I also had an assistant working correctly until yesterday and without having made any changes now it does not return the call data
But a trusted supplier must provide transparent and clear information, not this: https://status.vapi.ai/
m
@Shubham Bajaj Is there any rough ETA on getting this resolved?
n
Our organization is getting very affected by this issue 😩
k
@diddy for your case call terminated just after start of the call for which we don't generate the call summary
Btw, just to keep you in loop we are looking into it.
m
Thank you Sahil. As @vanjulen mentioned above though, you should update your status for transparency while this remains a problem
Is there any certainty that this will be resolved tonight? If not I unfortunately will have to use an alternative to VAPI as I cannot afford downtime tomorrow
k
A solution has been built and undergoing some testing right now. Will provide an update tonight or when it is merged, whichever comes first.
l
Keep getting notification that this is fixed. However it is not. I didn’t touch any settings or config. This was working for months and then 2 days ago my clients said they aren’t seeing any data. I have emailed support. I have sent Org ID, Call and assistant IDs. I’ve created new assistants. I’ve even created a new assistant in a different Organization. I haven’t received any update and I am still not getting structuredData. Please advise It has now been 2 days.
k
Hey Mike, we've fixed the issue. To use your analysis plan again, publish it again from the dashboard. Then, try 2-3 test calls and let me know how it goes.
m
Hi - I just tried this and it absolutely is not working! This is really urgent for me right now, is there any way to resolve it?
v
I understand how frustrating and urgent this situation is, especially since the suggested fix did not resolve the issue for you and others. The latest information indicates that the team believed the issue was fixed and asked users to republish their analysis plan, but it's clear from your feedback that the problem is still ongoing. At this time, there isn't any new update or alternative solution available in the information I have. Your continued feedback is important, and it's clear the team is aware that this remains unresolved for some users.
m
I republished from the dashboard, I can see all the structured data items there and yet none of this information is included in the payload delivered after the call
v
Since republishing from the dashboard hasn't resolved the issue, try updating your assistant's
analysisPlan
via the API, as this was previously suggested when dashboard changes weren't taking effect.
Here's an example API call to update the analysis plan:
Copy code
json
PATCH /api/assistants/{assistantId}
{
  "analysisPlan": {
    "structuredDataPrompt": "Your custom prompt here",
    "structuredDataSchema": { /* your JSON schema here */ }
  }
}
After updating, run a test call and check if the structured data appears in the payload. If the issue persists, please continue to report it to support for further escalation. Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update)
m
Tried it - didn't work
I sent the PATCH via API, everything remains the same: i.e. it is not working
v
Unfortunately, there is no new workaround available at this time, and both dashboard and API updates to the analysis plan have not resolved the structured data issue for you and others. I recommend escalating this with Vapi support and requesting that the incident be reflected on the [Vapi status page](https://status.vapi.ai/) for transparency. If you have not already, please continue to provide your organization and assistant IDs to support for further investigation. Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update) - [Vapi Support](https://docs.vapi.ai/support)
At this time, there is no new workaround or confirmed fix available beyond republishing from the dashboard and updating the
analysisPlan
via API.
Since these steps have not resolved the issue, the best course of action is to continue reporting the problem to Vapi support with detailed logs and call/assistant IDs for further escalation. Your feedback is important, and the support team is aware that this remains unresolved for some users. For reference: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update) Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update)
t
the structured schema is back n dashboard but on end call report it s totally missing ,why?this is the callerd id :b90aeed2-f376-435d-820a-6af2050bb2df
v
Since the structured data is still missing from your end-of-call report despite appearing in the dashboard, and all known workarounds have been tried, the best next step is to escalate this with Vapi support. Please provide your call ID (
b90aeed2-f376-435d-820a-6af2050bb2df
), assistant ID, and any relevant logs to [Vapi Support](https://docs.vapi.ai/support) for further investigation and to help prioritize a resolution. You can also request that this incident be reflected on the [Vapi status page](https://status.vapi.ai/) for transparency. Reference: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Support](https://docs.vapi.ai/support) Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Support](https://docs.vapi.ai/support)
t
callerd id:878a3f44-dbee-496b-b47f-aae3fba3cd4d man its not showing on the webhook the end call report is missing
v
Thank you for providing your call ID (
878a3f44-dbee-496b-b47f-aae3fba3cd4d
).
At this time, all known workarounds have been exhausted and the issue remains unresolved according to the latest documentation and support updates. To help escalate this further: Have you already submitted this call ID and any relevant logs to [Vapi Support](https://docs.vapi.ai/support)? This will ensure your case is prioritized for investigation. If you have, you may also request that the incident be reflected on the [Vapi status page](https://status.vapi.ai/) for transparency. Let me know if you need help with the support submission process. Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Support](https://docs.vapi.ai/support) - [Vapi status page](https://status.vapi.ai/)
k
It is fixed, can you try again?
l
Yes. It is included in structured data now šŸ™‚. However you’ve change the end call report and now those data is under analysis plan not under ANALYSIS where it was previously. Because of this when I go to Make and remap these fields to Airtable, now instead of the data it is showing {ā€œtypeā€:ā€stringā€} in the database instead of for example the actual name. Please please please can we get some type of notification before these kinds of changes. I now need to troubleshoot why this is happening. Yes your part is working now, Thank you but the frustration continues.
v
The structured data is now included in the end-of-call report again, but it appears that the data is located under the "analysis plan" section instead of the previous "ANALYSIS" section. This change is affecting integrations, as the data may now show up as a type definition rather than the actual value in external tools like Airtable. I understand how frustrating it is to have these changes happen without advance notice, especially when it impacts your workflow and requires additional troubleshooting. Your feedback about the need for better communication around such updates is completely valid.
s
Is the only way to fix this to manually add the structured data on the dashboard? Does it not work through API?
v
Thank you for your question. To help clarify: Have you recently tried updating the analysis plan via the API since the latest fix, and if so, did the structured data appear correctly in your end-of-call reports, or is the issue still present? Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [API Reference: Update Assistant](https://docs.vapi.ai/api-reference/assistants/update)
k
I'm sorry for the inconvenience. I'll share your feedback with the team. You can also do it via the dashboard, and it should work.
t
i see the schema in analysis plan but not the result ,the result is by far the most important thing man,
k
Can you share the latest call_id?
v
Thank you for sharing these details. To help us pinpoint the issue: Could you confirm if the structured data results (not just the schema) are visible in the Vapi dashboard for the same call, or are they missing there as well? This will help determine if the problem is with data extraction or just with webhook delivery. Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
s
v
Thank you for sharing your JSON schema. To help clarify: Are you able to see the actual structured data values (not just the schema) for "dnd" and "callback" in the Vapi dashboard for a recent call, or are only the type definitions (e.g.,
{ "type": "string" }
) visible there as well? Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
k
Nope, you don't need to.
v
Your structured data JSON format appears correct according to the documentation. To help pinpoint the issue: When you view the same call in the Vapi dashboard, do you see the actual structured data values (not just the schema), or are the results missing there as well? This will help determine if the problem is with data extraction or just with how the data is being delivered to your integration. Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
t
here it is 878a3f44-dbee-496b-b47f-aae3fba3cd4d
v
Thank you for providing the call ID. For call
878a3f44-dbee-496b-b47f-aae3fba3cd4d
, can you confirm if you see the actual structured data values (not just the schema) in the Vapi dashboard or via the API for this call? Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
t
no i can't see it man
v
Unfortunately, the structured data results are still not appearing in the dashboard or API, even though your schema is correct. This matches a known ongoing issue that is under investigation and currently has no new workaround. The best next step is to keep your support ticket open and monitor for updates from the Vapi team. If you haven't already, you can reference your call ID (
878a3f44-dbee-496b-b47f-aae3fba3cd4d
) in all communications for faster troubleshooting. Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
k
Just republish your assistant and try again.
j
Hi I duplicated a full functional assistant with end of call report working fine and extrating structured data, now in the new assistant it is not triggering the webhook. Both assitants no longer send this data to the webhook, amyone got a fix for this? It is a lengthy process to keep testing @User
k
Did you republish your new agents? Also, send me latest call_id.
j
Yes, I did republish. Here is three tests from yesterday where I can see in the analsys the structered data has been collected but not sent via end of call report fdd29b0f-2783-458f-ad26-bea87237397e e18f1375-1de6-4450-9b91-14182155db7f 1918edfb-d271-44b5-b55f-5cb7c5859582
v
At this time, there is no user-side fix for structured data missing from end-of-call webhooks, even after republishing assistants. The best action is to keep your support ticket open, reference your recent call IDs (e.g.,
fdd29b0f-2783-458f-ad26-bea87237397e
), and monitor for updates from the Vapi team as they work on a resolution. If you haven't already, ensure your ticket includes these call IDs for faster troubleshooting. Source: [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
Thank you for sharing the call IDs and confirming the structured data is visible in the analysis but not sent via webhook. To help isolate the issue: For one of these call IDs, can you check if the structured data appears in the API response for the call (not just in the dashboard)? This will clarify if the problem is with webhook delivery or with how the data is attached to the call record. [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
v
There is currently no user-side fix for the missing structured data in end-of-call webhooks, even after republishing or duplicating assistants. The best course of action is to keep your support ticket open, include your recent call IDs, and monitor for updates from the Vapi team as they work on a resolution. If you haven't already, ensure your ticket references the affected call IDs for faster troubleshooting. Source: [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
There is currently no user-side fix for the missing structured data in end-of-call webhooks, even after republishing assistants. The best action is to keep your support ticket open, reference your affected call IDs, and monitor for updates from the Vapi team as they work on a resolution. If you haven't already, ensure your ticket includes the latest call IDs for faster troubleshooting. Source: [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) Source: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
k
Checked the logs for this call id fdd29b0f-2783-458f-ad26-bea87237397e The reason why end-of-call-report was not sent because it was not able to find the serverURL where to send the data. šŸ”µ 04:30:26:097 No serverUrl found for message type: end-of-call-report. Skipping...
j
That doesn't make sense as I checked this, deleted the webhook url, re-added and republished, I did not make any calls without this url saved as per the attached image, I have also tested the webhook by sending data directly from my GHL and it works fine. I can see a lot of complaints about the end-of-call report, if there is a fix on its way or has been fixed let me know, if not, then maybe Vapi is not the solution for my business. https://cdn.discordapp.com/attachments/1375115350693380200/1376497981770960978/image.png?ex=68358b24&is=683439a4&hm=ee670ee118ecf990aa7834acd153c425daaf3bc9e20a2cd851855886d13a4291&
v
There is currently no user-side fix for the missing end-of-call webhook, even if your server URL is correctly configured. The best action is to keep your support ticket open, include your affected call IDs, and monitor for updates from the Vapi team as they work on a resolution. If you haven't already, double-check that your server URL is set at the assistant or account level, as per [server URL priority documentation](https://docs.vapi.ai/server-url/setting-server-urls). If the issue persists despite correct configuration, it is a known platform-side bug and requires Vapi engineering intervention. Sources: - [Setting server URLs](https://docs.vapi.ai/server-url/setting-server-urls) - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis)
There is currently no user-side fix for the missing end-of-call report webhooks, even if your server URL is correctly configured and republished. The best action is to keep your support ticket open, include your affected call IDs and configuration screenshots, and monitor for updates from the Vapi team as they work on a resolution. For reference on server URL configuration and priority, see the [Vapi documentation](https://docs.vapi.ai/server-url/setting-server-urls). Sources: - [Call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) - [Setting server URLs](https://docs.vapi.ai/server-url/setting-server-urls)
k
Hello JayK, You are currently using the Transient Assistant for this callid fdd29b0f-2783-458f-ad26-bea87237397e, but it does not have any server.url associated to it. This is why you are not receiving end-of-call reports. You can refer to this link for instructions on how to set up the server.url correctly for Transient Assistants:
j
Thanks I will stop wasting my time here and get building in another software
Hi has this issue been fixed yet, I have not tested but always had a sever.url as it worked previously. I can see when I was having this issue so were many other users
k
It is fixed.