https://vapi.ai/ logo
Join Discord
Powered by
Not receiving transcript messages on the server UR...
# support
n
Over the past couple of days we've stopped receiving transcript messages to the server URL. Receiving the end of call report, status update and conversation update. However the transcript messages - both partial and full - are missing. This is an important requirement for us - please address this soon.
v
Hi @Neeraj, 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**: * [Update Assistant]() * [Server URLs]() * [Create Assistant]() * [Get Assistant]() -----------------------------
### Answer It sounds like there might be an issue with the configuration of the server messages or a temporary service disruption affecting transcript messages. 1. Check Server Message Configuration: Ensure that the 
transcript
option is included in the 
serverMessages
configuration when setting up or updating your assistant. The 
serverMessages
array should include 
transcript
to receive both partial and full transcript updates [(1)]() . 2. Review Documentation: Double-check the server URL and server message configuration guidelines to ensure everything is correctly set up according to the [Server Events documentation](). 3. Temporary Service Issues: There might be temporary disruptions or bugs affecting the transmission of transcript messages. Review the status updates or contact the support team to inquire about any ongoing issues. If the configurations are correct and there are no reported service disruptions, you might need to reach out to the support team for a more detailed investigation into why the transcript messages are not being received.
Got it. Tagging @User for additional help.
s
Can you send me a call_id or anything so that I can look into it?
n
It is happening universally for all calls over the past few days, both inbound and outbound. Here is a recent call: ee51b462-37ea-4713-8c47-df9f8dc4801e
Another user has reported this issue in the general channel as well.
s
{ "message": { "message": "Request failed with status code 400", "data": "Invalid message type." }
As per I can see that, you are not handling the data properly from your end.
n
It was working fine until a few days ago - also I'm logging ALL the calls being made to the endpoint. The transcript related calls are not showing up any more.
Can you share the specs of this particular request? I'd like to compare it with the earlier requests to see if anything has changed.
s
Check your DM
n
That is a 'conversation-update' type message - I'm already receiving these. I have mentioned this in the ticket. I'm referring to 'transcript' type messages which include a transcriptType that is either 'partial' or 'final'. Those are the ones that have stopped coming.
Please let me know if the issue is clear to you now or not.
s
Ah, I see let me check.
n
Hey Sahil, can you confirm that this is indeed an issue on your end - just for clarity on our side.
p
if it helps i've been getting transcripts without issue using the end of call report.
n
Yeah, I'm receiving the end of call report too (as mentioned in the ticket) but we need the live transcript as the call is ongoing ('transcript' type messages). Which was working fine until a couple of days ago.
s
@Neeraj Yes, it seems to be a bug in the Transcript Server Message. I have forwarded it to the team to fix.
n
@Sahil Hey Sahil, any ETA on this?
s
We are working on it. As soon as it is fixed, I will ping you!
n
@Sahil Hi there, it seems that this still hasn't been fixed. Please provide an ETA - this is very frustrating as this is part of the core VAPI server URL architecture and it's an important requirement on our end for an upcoming demo as well.
s
I am looking into this @Neeraj I will update you as soon as it is fixed.
@Neeraj can you try once more it is fixed.
n
@Sahil Still no transcript messages - only the other ones, like before.
s
It will be released by tonight. The PR has been merged.
n
@Sahil The issue has been resolved. Thanks.
7 Views
PreviousNext
Powered by