This happens quite randomly when an agent is updated and published from UI. Our other agents are working fine but since last few days we have noticed when we make any updates to the agent, they suddenly change the payload structure in the server webhook to our backend.

Hi there! 👋 I understand your frustration with the missing

assistant.id

and

assistant.parentId

in the end-of-call report and the changing payload structure in your server webhook. I'm unable to determine the exact reason why this is happening randomly for your specific agent updates. However, I can definitely help with information about these known issues in Vapi! Based on the information I found, this is a recognized issue where agent updates can cause missing data in end-of-call reports and changes in webhook payload structures. Several other users have reported similar problems after updating their agents. ## Missing Assistant IDs in End-of-Call Reports This exact issue has been reported by other users, where

assistant.id

and

assistant.parentId

stop appearing in the end-of-call report after an agent is updated and published from the UI. According to the information I found, this happens "quite randomly when an agent is updated and published from UI" - matching your experience exactly. ## Changes in Webhook Payload Structure The sudden change in payload structure in the server webhook after agent updates is also a documented issue. After making updates to an agent, the payload structure in the server webhook to the backend can unexpectedly change. ## Potential Causes Several factors might contribute to these issues: 1. **PATCH Request Behavior**: When updating an assistant using PATCH requests, nested properties can be overwritten by default. To preserve all properties, both updated and previous properties must be passed in the request. 2. **Reverting to Older Versions**: Updates can sometimes cause an assistant to revert to a previous version, which can lead to unexpected behavior. 3. **Configuration Issues**: Agent updates can lead to configuration issues that affect data transmission. 4. **API Changes**: Updates to the Vapi API itself can cause changes in the expected payload structure.

Here's an example of a previous payload where vapi was sending assistant.id in it and here's after when its no longer sending this id anywhere in the payload https://cdn.discordapp.com/attachments/1357407046370328638/1357408766521245886/image.png?ex=67f018ed&is=67eec76d&hm=dd2f091f646e72262332649a71bddcb5fe4ceaacb47ea1abb3ac97a675e8993c& https://cdn.discordapp.com/attachments/1357407046370328638/1357408766777233592/image2.png?ex=67f018ed&is=67eec76d&hm=2163bfe7670240a5102412801afce12213ecddccaad349ea7d553a165cbe633a&

checking if this is resolved/solved for you?