Hello, I am encountering an issue related to metadata handling in the call-ended and call-analyzed callbacks. Scenario: Once the call is established, I am using the update-call route to add certain keys to the metadata based on the call id. which I expect to receive at the time of call-analyzed and call-ended events. however even though the metadata gets successfully updated i am not receiving the updated metadata. What could be the issue? Additionally, I do not see any relevant entries in the logs for the update-call events, which makes it difficult to debug whether the update is being processed correctly on the backend.I can share specific call IDs where this issue occurred if that would help with the investigation.

this isn't best practice, the metadata gets a new cloned state at the start of the call and isn't replicated

i believe that's the purpose of the update-call API as per the description in current documentation https://docs.retellai.com/api-references/update-call @Colin - Integrations @ Retell AI. wherein we can update the internal details in the metadata object and can later get this field from the call object.

you're able to update it, but it gets overrided with internal metadata

I’d like to clarify the expected behavior of the /update-call endpoint based on the current documentation. Our understanding is: - If an API allows updating metadata, - And the documentation states that it updates the existing call object, Then the updated metadata should remain consistent and be reflected in: - Throughout call record. - The call-ended webhook payload. - The call-analyzed webhook payload. Right now, it appears that metadata updated via /update-call is not present in the end-of-call callbacks, which suggests that the updated state is not persisted through the full call lifecycle. Additionally, the updated metadata was previously reflected in the final call data. Could you please check whether any recent changes may have affected how metadata updates are handled or persisted?

this should only be used after the call for storage settings, i'll let you know what the team says as a workaround for your case

Yup i've got a certain call related data which will only be generated post call is connected, and those details are required in the call analysis events.

As said before this is currently only used to update stuff mid call and used for storage, any other states right now are not replicated. I’ve escalated your use case to the product team

@Colin - Integrations @ Retell AI any updates from the team yet ?