Hello, lately we've been running into a bunch of issues with call logs saying Invalid DateTime and Twilio Connection Failed. There's no data in the call log so it's hard to troubleshoot. But when sending the create call request there is no error and it seems it all goes through correctly. When we get the end of call report is where it seems everything is empty. Anyone else having this issue? Super weird because this doesn't happen with all calls, some work fine https://cdn.discordapp.com/attachments/1328716389090988054/1328716389464412282/Screen_Shot_2025-01-14_at_2.24.15_PM.png?ex=6787b711&is=67866591&hm=5681af9bd12896550658c00c8c3abf875d111fa80baf63b104c7e60cf54d3e0b&

@juliana Hello! I'm sorry to hear that you're experiencing issues with call logs and Twilio connections. It sounds like there might be intermittent problems either with the data being sent to Twilio or with the response handling in your system. For the "Invalid DateTime" issue, it's important to ensure that the timestamps being sent in your create call requests are in the correct format expected by Twilio. Twilio typically expects timestamps in ISO 8601 format. If the format is incorrect or the data is not being sent properly, it could result in invalid entries in your call logs. Regarding the "Twilio Connection Failed" issue, this could be due to a variety of reasons such as network issues, incorrect Twilio credentials, or problems with Twilio's service. Since you mentioned that some calls work fine, it's less likely to be a credential issue and more likely to be an intermittent network or service issue. To troubleshoot these problems, you can: 1. Double-check the date and time formats in your create call requests to ensure they comply with Twilio's requirements. 2. Review your network logs to see if there are any connectivity issues at the times when the Twilio connection fails. 3. Check Twilio's status page to see if there were any service disruptions around the time you experienced the issues. 4. Contact Twilio support with specific call SIDs (unique identifiers for calls) that failed to get more detailed information on why those calls didn't connect or why the logs are empty. If you need further assistance or if you'd like me to help with any specific checks or logs, please let me know!

@juliana could you share any of the recent call id so I can take a look?

14107278-8be8-4aba-9deb-db9d75e7b269 39e51a75-0675-4c55-a760-4380951a92b1 18005136-c4e4-4135-9b0e-17c6f6a53551 df6194f6-9cf3-4d08-b02f-cfa25b4e11b0 @Shubham Bajaj thank you!

🔵 15:16:01:775 Call

18005136-c4e4-4135-9b0e-17c6f6a53551

Waited 300s But Transport Never Connected. 🔵 16:15:56:421 Call

14107278-8be8-4aba-9deb-db9d75e7b269

Waited 300s But Transport Never Connected. @juliana Looks like the issue from the Twilio side, like we sent the request to connect the call but we didn't got any response from their end.