VAPI•3mo ago

end-of-call-report with stale call object

In the

end-of-call-report

end-of-call-report

it seems like we are getting a stale call object where the status is still

queued

queued

queued

queued.

I have checked a couple of cases and we did receive the

end-of-call-report

end-of-call-report

after the call was ended but the call object in the report does not reflect the correct status (and also missing fields that I would expect in an ended call).

My expectation is that the call object in the report should be exactly the same as the one if I use the

GET /call/:id

GET /call/:id

GET /call/:id

GET /call/:id endpoint. This is not the case currently.

Example call ids:

0199bd84-143a-7008-b70b-40097256f731

0199bd84-143a-7008-b70b-40097256f731

0199bd84-143a-7008-b70b-40097256f731

0199bd84-143a-7008-b70b-40097256f731

0199bdc6-00d0-7ee0-bb73-889bcc829e90

0199bdc6-00d0-7ee0-bb73-889bcc829e90

0199bdc6-00d0-7ee0-bb73-889bcc829e90

0199bdc6-00d0-7ee0-bb73-889bcc829e90

Iincredible-moccasin In the `end-of-call-report` it seems like we are getting a stale call object whe...

military-pink•10/7/25, 4:55 PM

What are you trying to extract from end of call?

KyleAPP•10/9/25, 12:36 AM

We are seeing in the logs this line:

🔵 07:16:06:559 Call ended with reason: customer-ended-call

🔵 07:16:06:559 Call ended with reason: customer-ended-call

The end of call report was sent after this line. Do you have call-status serverMessages enabled? If so, you might want to disable them for the time being to see if the end of call report continues to send with missing fields and queued call statuses.

incredible-moccasinOP•10/9/25, 7:30 AM

I can see the call object in the message has a

updatedAt

updatedAt

field same as

createdAt

createdAt

so it does look like a stale object. I can also see this being sent after the call has ended and in the message payload (outside of the call object) it has the correct

endedReason

endedReason

incredible-moccasinOP•10/9/25, 7:35 AM

I have tried what you suggested - removed all message type under Server MessagesServer Messages and only leave

end-of-call-report

end-of-call-report

. I can see the

end-of-call-report

end-of-call-report

message still contains a stale call object.

Iincredible-moccasin I have tried what you suggested - removed all message type under `Server Message...

military-pink•10/16/25, 4:18 AM

Are you using an automation on the side??

incredible-moccasinOP•11/3/25, 6:41 AM

what do you mean by automation?

KyleAPP•11/3/25, 11:17 PM

We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old.

With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.

incredible-moccasinOP•11/13/25, 8:02 AM

hello we are still experiencing this issue - we can probably unblock ourselves by making another call to fetch the latest call object. Just wonder if this behaviour of stale call object in the end-of-call-report is expected or a bug

KyleAPP•11/18/25, 4:45 AM

It seems like a bug. Could you please share logs with the stale object? I want to bring it up to the team if it is still occurring

end-of-call-report with stale call object

Similar Threads

Similar Threads

Similar Threads