----------------------------- **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.

🔵 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.