We have noticed that for the last one month, Call recordings for most of our calls are missing. We have integrated S3 for storage on VAPI. Some calls have all recordings, some has only stereo, some has mono and none for some calls. Call id - 019ab494-b876-711c-bf06-fd1507b8aafa - Has no recordings data Call id - 019ab4e4-9e98-722d-84ba-05c7a82cfb30 - Has stereo Due to this issue, Call recording url is missing from VAPI /call/:callid endpoint response. We have not changed any config or code from our side since last 2 months. Please provide some solution for the above issue. Also is there a way to retrieve the missing call recordings.

To address missing call recordings with S3 integration, please verify your assistant's

artifactPlan

configuration, especially the

recordingEnabled

,

recordingFormat

, and

recordingPath

properties. Here’s an example configuration:

json
"artifactPlan": {
  "recordingEnabled": true,
  "recordingFormat": "mp3",
  "recordingPath": "/your-path/"
}

Double-check your S3 bucket permissions and ensure the path is correct. If recordings are still missing, unfortunately, there is no documented way to retrieve them retroactively. For more details, see the [Vapi call recording documentation](https://docs.vapi.ai/call-recording). Source: - [Call recording](https://docs.vapi.ai/call-recording)

This issue is likely caused by Vapi’s recording system failing to upload or generate some recordings, since your setup hasn’t changed and the problem is inconsistent. Share the affected call IDs with Vapi support so they can check their recording pipeline, fix any upload errors, and try to recover missing files. In the meantime, keep an eye on your S3 bucket to verify which recordings are actually being received.

Has this issue been resolved? I have just experienced the same thing... call recordings were all available on my account, now I came to check some recent logs after a few calls came in and all previously available call logs all disappeared all the way back to Nov 21st...

How to contact Vapi support?

Hey Akshat, instead of using the call/:callid endpoint, just cut it down to the /call API endpoint I tried using the callid endpoint, and I got a 404 error, even though the /call endpoint returned all calls up to the most recent one, with callid associated (the same callid that returned a 404 error) This was my comment on another related chat, I'll just paste below for reference: Unfortunately VAPI support isn't available on weekends... brutal for the kind of service they offer lol. In any case, I thought I'd come and benefit the group if possible. I just experienced the same issue, and I was very worried, this would cause a huge headache with all my clients. I ended up going through the VAPI API to retrieve calls, I was able to see the full list of my calls and it provides the recording URLs too. This seems to be a VAPI frontend UI issue, hope they fix it soon. Use the following API call: curl -X GET "https://api.vapi.ai/call" -H "Authorization: Bearer YOUR-API-KEY" \ -H "Content-Type: application/json" This will list all your calls (up to 100 records I believe), and then you can parse through it to find the calls you want to review, and the associated call recording URL

Thanks @EliteOath I'll try this. But we are actually using S3 to store the call recordings. I am not able to find the call recordings manually in our S3 bucket too.

support@vapi.ai This is their official support email @Akshat Jain

only stereo 019b63c8-dbf8-711a-ad96-9bdd3d516c63 Only one mono 019b6397-f9da-755e-92a7-530b6232a905 No recordings 019b7442-b46c-7ffe-9b29-2668d2be766e

Hi Akshat, Yes, the upload to AWS S3 failed for these recordings. We are currently investigating the issue and will update you as soon as we have more information.

Sure Thanks for informing

No, sadly, there's no way to recover now as the upload failed.

Yeah ok. No worries. For now I am switching to VAPI's default storage. Let me know once the issue is resolved.

sure, I'll let inform you know when done.