Potential Compliance Risk: Structured Output Mismatch Across Calls It appears that structured outputs are being incorrectly associated between calls for Agent ID

85b4dbe4-57fc-4525-951c-d220a3556dd8

. We made the following two calls to this agent: 1.

019df92a-6179-7001-83f5-a6a26031055a

2.

019df939-f1c4-7ddb-ac17-da5a99d6b628

After reviewing the transcripts and outputs, we observed that the structured output attached to call

019df939-f1c4-7ddb-ac17-da5a99d6b628

appears to have been generated using the transcript from call

019df92a-6179-7001-83f5-a6a26031055a

. Additionally, call

019df92a-6179-7001-83f5-a6a26031055a

does not appear to have any structured output associated with it. This suggests there may be an issue where the LLM or post-processing pipeline is accessing the wrong call transcript while generating the final structured output. This is a significant compliance/privacy concern, as downstream systems may process and act on outputs belonging to a different user interaction. Could you please help investigate what might be causing this behavior?

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

That’s a pretty serious issue, especially if VAPI is attaching structured outputs to the wrong call transcripts. It usually comes from async race conditions, shared memory/context reuse, or webhook processing mismatches between calls. I can help you trace where the mix-up is happening and tighten the mapping flow to avoid cross-call leakage. Are you handling the structured output through VAPI webhooks directly or passing it through another backend layer first? @Nano

Hey, Can you provide the call ID for a recent call so we can investigate the issue further?

Priyanshu Ranjan , 019df92a-6179-7001-83f5-a6a26031055a 019df939-f1c4-7ddb-ac17-da5a99d6b628 these were the call ids i observed it at @Matt handling the structured output from end of call report from vapi, i have a server that listens to this and then it processes the output and forwards it to another system.