😭 Unknown Error in logs if call is longer than 10...
# support
m
Shorter calls are processed fine, but longer calls have what seems to be a 1 in 2 chance that it says Unknown Error in Call Logs. This is really problematic, since it doesn't fire the end-of-call-report webhook, so my make.com integrations dont work at all. Also there is no transcript or logs if Unknown Error, so I can't debug on my own. https://cdn.discordapp.com/attachments/1287953051344306206/1287953051620999210/image.png?ex=66f36b40&is=66f219c0&hm=f57d053ac93274cea5fed391628f38ebb21219e33c62dd498a4ec3a40cbadb03&
v
@Mehar I'm sorry to hear that you're experiencing issues with longer calls resulting in an "Unknown Error" in your Call Logs. It's important that we get this resolved so your end-of-call-report webhook and make.com integrations can function properly. To assist you better, I would need to gather more information about the specific circumstances under which this error occurs. Could you provide details such as the approximate duration of calls when this error tends to happen, and if there are any commonalities between the calls that fail? In the meantime, I recommend reaching out to our support team to report this issue. They can help investigate the problem further and provide you with the necessary assistance to resolve it. If there's any additional support I can offer, please let me know.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
m
@User If you could please look into this ASAP since I am unable to launch this assistant in production for my client β€” losing money from this error πŸ™
s
call_id pls
@Mehar
also, if you are using it via web sdk
then there is some issue related supabase storage
and it should be fixed by tomorrow
we are doing migration
m
Amazing okay. Actually I haven’t noticed it since sep 23 EST until now. If it happens again today I’ll send call_id πŸ‘
8 Views