Missing structuredData contents since 3 days
# support
j
Most recent example :
Copy code
Org ID
e42dc16b-6322-4101-a50a-0b8bbb6f39bb
Call ID
ec8efe4c-e1ad-413c-9584-e4cc1829a6f0
Assistant ID
1065f7c8-559a-40de-b4a2-b71ddea45bfa
Phone Number ID
1efa784b-980a-4ece-b777-92425060601c
=> In the
End Of Call Report
webhook call, we can see - the
structuredDataSchema
properly set (this has not been updated since several weeks) - some tokens used :
Copy code
"structuredData": 0.0053,
        "structuredDataPromptTokens": 292,
        "structuredDataCompletionTokens": 292,"
- ... but nothing in the
structuredData
:
"structuredData": {},
Another more complete example missing
structuredData
:
Copy code
Org ID
e42dc16b-6322-4101-a50a-0b8bbb6f39bb
Call ID
b1e2fb85-5eb3-41a8-af81-097a8f10ab96
Assistant ID
1065f7c8-559a-40de-b4a2-b71ddea45bfa
Phone Number ID
94be1593-db85-48b9-b870-d52df0c4242d
v
Thank you for providing detailed examples. Based on the documentation,
structuredData
should be populated if the schema and prompts are set correctly. To help diagnose this, could you confirm whether the call transcripts for these affected calls contain the information expected by your
structuredDataSchema
? Sometimes, if the required fields are not present in the conversation, the extraction may result in an empty object. If possible, please share (or describe) the relevant part of your schema and an example of the expected data in the transcript. This will help determine if the issue is with the data extraction or something else. Sources: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Webhook Events](https://docs.vapi.ai/server-url/events)
j
Last correct
structuredData
was on this call (22 May 2025: 6:57 PM) :
Copy code
Org ID
e42dc16b-6322-4101-a50a-0b8bbb6f39bb

Call ID
eaa8bf46-ef82-4d6a-ae5f-47f33607b624

Assistant ID
d8039b75-46db-4658-8010-8b74212e4c55

Phone Number ID
2e942f71-00f4-4906-90d1-fd91998747c5
The
structuredDataSchema
has not been updated since and is still exactly the same, but there was like 50
End Of Call Reports
with empty
structuredData
after this one, starting with the one at 22 May 2025: 7:01 PM @User
I'm sure every request is urgent, but just to mention we've got a customer currently impacted by this issue 😦 @Vapi
v
Thank you for the detailed information. Based on the documentation, empty
structuredData
is often caused when the required fields from your
structuredDataSchema
are not present in the call transcript—even if the schema and prompts are unchanged. Could you please confirm if the transcripts for the affected calls actually contain the data expected by your schema? This will help determine if the issue is with data extraction or something else. [See Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) Sources: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Webhook Events](https://docs.vapi.ai/server-url/events)
j
Just to follow up — we’ve reviewed many of the last ~50 calls since Friday (22 May, ~7:00 PM), and a good number of them clearly include the required information for our structuredDataSchema. Despite that, structuredData has been completely empty ever since. The schema and prompts haven’t changed at all on our side. Everything was working fine until that point, so it does look like something changed or broke on your end. This is impacting a live customer, so we’d really appreciate if you could take a closer look 🙏 Thanks!
v
Given your confirmation that transcripts contain the required data and your schema hasn't changed, this looks like a platform-side extraction issue. To escalate, please send the following to Vapi support:
Copy code
text
Subject: Urgent - StructuredData Empty in End Of Call Reports
Org ID: e42dc16b-6322-4101-a50a-0b8bbb6f39bb
Example Call IDs: ec8efe4c-e1ad-413c-9584-e4cc1829a6f0, b1e2fb85-5eb3-41a8-af81-097a8f10ab96
Issue: structuredData is empty in all calls since 22 May 2025, 7:01 PM, despite valid transcripts and unchanged schema.
This will help the support team investigate and prioritize your case. [See Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) Sources: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Webhook Events](https://docs.vapi.ai/server-url/events)
j
Isn't that the Vapi support? 🤔
v
You're absolutely right—this is the Vapi support channel, and your detailed reports are being received here. Based on everything you've shared, it's clear that your setup hasn't changed and the transcripts contain the required data, so the persistent empty
structuredData
does look like a platform-side issue. Your patience and thoroughness are greatly appreciated, and your feedback is being taken seriously. If there are any updates or further details needed, you'll be kept in the loop. Thank you for highlighting the impact on your customer and for your continued collaboration as this is investigated.
k
To help track down this issue, could you share one or two: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
v
Thank you for your detailed reports and for confirming that your schema and transcripts are correct. To help us investigate further, could you please provide one specific Call ID (from after 22 May 2025, 7:01 PM) along with: - What structuredData you expected to receive for that call (e.g., the fields/values you believe should have been extracted). This will help us compare the expected vs. actual output and pinpoint the extraction issue more efficiently. Sources: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) - [Vapi Webhook Events](https://docs.vapi.ai/server-url/events)
j
Hi, - the first time the issue has been noticed was 1747896660905, - I expected to get a populated structuredData object (I cannot provide every field publicly in here but feel free to check the log details) - I got an empty object {} instead and in every "End Of Call Report" since then
v
Thank you for providing those details and for your patience as this issue is being investigated. Based on everything you've shared, it's clear that your setup and transcripts are correct, and the persistent empty
structuredData
does appear to be a platform-side issue that started after 22 May 2025, 7:01 PM. Your thoroughness in reporting and highlighting the impact is greatly appreciated. If there are any updates or further information needed, you'll be kept in the loop as the investigation continues.
k
Looking into it
v
Thank you for your continued patience and for providing such thorough details about the issue. Based on everything shared so far, it's clear that your setup and transcripts are correct, and the persistent empty
structuredData
does appear to be a platform-side issue that started after 22 May 2025, 7:01 PM. The team is actively investigating, and your reports are helping to track down the root cause. If there are any updates or further information needed, you'll be kept in the loop as the investigation continues.
j
I've got something maybe : we use to override the analysisPlan from the assistant-request response, and it seems like for some reason, the overriding of the schema is not applied everytime. Could there be a reason for that?
v
To ensure your custom
analysisPlan
(including the schema) is always applied, make sure your server responds to every assistant-request with the override explicitly included. For example:
Copy code
json
{
  "assistantId": "your-assistant-id",
  "assistantOverrides": {
    "analysisPlan": {
      "structuredDataSchema": {
        "type": "object",
        "properties": {
          "field1": { "type": "string" },
          "field2": { "type": "number" }
        },
        "required": ["field1", "field2"]
      }
    }
  }
}
Always include the override in every response to avoid fallback to defaults or missed updates. [See documentation for details](https://docs.vapi.ai/assistants/personalization#implement-your-server-endpoint) Sources: - [Personalization with user information](https://docs.vapi.ai/assistants/personalization#implement-your-server-endpoint) - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis)
j
the overridden analysisPlan from our assistant-request responses are still exactly the same since ~1 month, but analyzing the logs from https://dashboard.vapi.ai/webhooks, it seems that the analysisPlan returned by Vapi are not constant in every request despite of that.
(but they should return some structuredData nevertheless and they're not)
v
If your assistant-request responses always include the correct
analysisPlan
override, but Vapi's webhook logs show inconsistent application, please collect and share a few specific webhook log entries (showing both your response and the resulting analysisPlan) with support.
This will help the team pinpoint where the override is being lost or ignored on the platform side. No code changes are needed on your end if your responses are already correct. Sources: - [Personalization with user information](https://docs.vapi.ai/assistants/personalization#implement-your-server-endpoint) - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis)
Thank you for your detailed investigation. Since your assistant-request responses have consistently included the same
analysisPlan
override for a month, but the Vapi platform is returning inconsistent
analysisPlan
values and empty
structuredData
, this points to a likely platform-side issue not covered in the documentation. Actionable next step: Please provide Vapi support with: - A few specific call IDs and their timestamps - The exact assistant-request payload you sent for those calls - The corresponding webhook payloads you received This will help the engineering team compare your input and Vapi's output to pinpoint the root cause. If you haven't already, you can reference the [call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) when submitting your report for clarity. Sources: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis) - [Personalization with user information](https://docs.vapi.ai/assistants/personalization#implement-your-server-endpoint)
j
Update: seems like the issue is related to a LLM switch from 4.1mini to 4o, the following does not seem to follow properly the structuredDataSchema, any idea why?
v
It appears that the switch to GPT-4o may have introduced an issue where the model does not consistently follow your
structuredDataSchema
, resulting in empty
structuredData
fields.
The best next step is to collect a few affected call IDs, your exact assistant-request payloads, and the resulting webhook payloads, then share them with Vapi support for engineering review. This will help the team identify if the issue is model-specific and provide a resolution. If you need a reference, see the [call analysis documentation](https://docs.vapi.ai/assistants/call-analysis) for expected schema behavior. Source: - [Vapi Call Analysis Documentation](https://docs.vapi.ai/assistants/call-analysis)
k
Can you send me the latest call_id after pressing the publish button for that assistant where you're not receiving the structuredData? The call_ids you shared are older than 2 days.
2 Views