Structured Output empty on critical call
# support
r
Hello, one my Structured Output returned an empty json after a call for some reason. It should've been populated with the set fields and informations that was supposed to gather. I wanna understand why that happened and if it will happen again. Call id: 019dfb1a-7e7e-7000-8117-ae10658eac5c Timestamp: 6 May 2026 at 12:30:28 UTC+10 Structured Output: Name: Real Estate Lead Call Id on response: 3d1d76bc-0163-427a-9c05-bf72fcc5a172 Expected result:
Copy code
{
funding: "pre-approved"
handoff: {
needsHandOff: false
}
callBack: {
busy: false
}
voiceMail: false
manualCheck: {
required: false
}
notInterested: false
meetingDetails: {
timeOfMeeting: "11:45 AM"
scheduledAMeeting: true
dateOfMeetingDDMMYYYY: "07-05-2026"
}
propertyDetails: {
budget: "$600,000 - $800,000"
rawBudget: "750 k"
forInvesting: true
forCapitalGrowthYieldOrBoth: "Capital Growth"
locationsInterestedInForPurchase: "Perth"
}
clientAskedForInPersonMeetingAndYouAgreed: false
meetingNotScheduledButInterestedInFutureMeeting: false
}
Actual result: {}
v
To diagnose why your structured output was empty, go to your Vapi dashboard and navigate to Observe > Call Logs, then select the call with ID
019dfb1a-7e7e-7000-8117-ae10658eac5c
. Review the transcript and structured output section to check if the required information was present and if any extraction errors were logged. This will help you pinpoint if the issue was due to missing data, unclear schema descriptions, or another extraction problem. Tip: Update your schema field descriptions for clarity if you notice variables are not being extracted as expected. Source: - [Debugging voice agents](https://docs.vapi.ai/debugging)
r
That was not helpful. I already debugged the call, all the information was there, the "expected result" provided was extracted from the deprecated Analysis log from the same call, so the information is definetely there. Also, different calls from the past and the future had the Structured Output filled as expected
Please I need a response on this!!
It happened again
@User @User
Call id: 019e33f7-5e2c-7001-b690-c72387de38c1