No recording Urls in some end of call reports
# support
s
And this is huge concern as my users need the audio to refer back to. 1ce4f9ad-e013-4027-9c7f-87e41b0c86a2 7c351d81-5f6b-46ed-a87e-74d57a7b4d25 096044e6-a1d9-45c1-adea-f4c53b49517a
v
Hi @Sangy, I'm an AI assistant for Vapi. I'll analyze available sources and get back to you shortly.
----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Inbound Support Example]() * [Create Assistant]() * [Update Assistant]() * [List Assistants]() -----------------------------
### Answer I understand the importance of having access to call recordings for your users. In situations where the end-of-call report does not include the recording URL, it could be due to several factors, such as the recording feature not being enabled for that specific call, or an issue during the call that prevented the recording from being captured or processed correctly. According to the Vapi documentation, the
recordingUrl
is provided in the end-of-call report if the call was recorded. If recordings are crucial for your application, ensure that the
recordingEnabled
attribute is set to
true
when creating or updating your assistant [(1)]() [(2)]() . If the issue persists despite having the recording feature enabled, it might be beneficial to review the call details and configurations to identify any discrepancies or issues that might be preventing the recording URLs from being included in the end-of-call reports. For instances where there's an unexpected absence of recording URLs, it's recommended to check the call configurations and ensure that all prerequisites for recording are met. If the problem persists, it may require a more in-depth investigation into specific call logs or configurations, which isn't directly covered in the provided documentation.
s
Looking into it.
šŸ”µ 17:20:41:904 Uploading Recording... šŸ”“ 17:20:42:911 Couldn't Upload Recording. Error: { "statusCode": "500", "error": "Internal", "message": "Internal Server Error" } Seems Supabase had an Internal Server Error. Never seen it, odd. Let me know if it happens again.
s
ok thanks
4 Views