VAPI API issues with timestamp data
# support
a
Copy code
{
  "role": "bot",
  "time": 1749975913163,
  "source": "",
  "endTime": 1749975909595,
  "message": "Hello. I am alex, your AI interviewer. How are you today?",
  "duration": 2080,
  "secondsFromStart": 1749975906715
}
secondsFromStart
for only some calls, it's giving this absurd epoch time. Is this a known bug? https://cdn.discordapp.com/attachments/1386957634770436237/1386957635160641578/image.png?ex=685b9874&is=685a46f4&hm=a90b4d0d1f9d05296f0da9527d6482db5117de5872862d91e4b308ee8aa4a91f&
v
Hi, could you please share some call logs where the seconds is not in epoch format?
a
Hi Kyle. Sorry, I didn't get notified on this. I have attached screenshot of an affected logs. Can you tell what specifically do you want to see?
v
No worries, if you could please send a call id from your call logs section and attach to this ticket for our investigation it would help us out. Additionally, please make a new test call and send that call id
a
This issue happens randomly with some calls. Eg CallID with issue:
f96a0931-2f29-4cce-ba5d-e60afb54f8ec
Eg CallID without issue:
81548d7c-dd5d-4647-bddd-9b4fedc4207f
And note that I have seen this issue more often with long calls (> 45 mins). In the recent 10 calls, I didn't see this issue. But can you please confirm from your end if this issue is really resolved since our evals completely depend on this
v
Let me look into these call id logs and get back to you on that
a
Sure! And I request you to tag me or reply to my comment so that I get notified. It adds unnecessary delays in to-and-fro communication otherwise 😦
k
@Ashhar this looks like a rare occurence as I am not able to reproduce this issue. If it occurs again, please let us know and provide another call id
a
Ohk. Sure. Thanks