results.getResult Transcript
hello, i'm trying "Transcript Beta" tool of typebot and i'm getting this error "results.getResult Transcript". Any fix?
23 Replies
Should not happen, can you provide more info on how I can reproduce it on my end?
I suspect the issue might be related to the list of buttons implementation (see screenshot). Before using this implementation, I didn’t have this problem.
Sure, what kind of information do you need from me to reproduce it on your side?
telemedicina-chatbot this is the typebot id
Just tell me from scracth how I can create a very simple bot that reproduces this issue
this is the export flow
Let me know if this information is enough for you to reproduce the issue or if you need any additional details.
Thanks I managed to reproduce, will fix it today
I still have the same problem
can u give me some news?
just to add some context: this feature is quite important for the project I’m working on. I would need it to be available reasonably soon, as we’re integrating Typebot into a telemedicine platform, which could also bring good visibility to Typebot within our company and our partners.
If this feature cannot be supported or there is no clear workaround, I will unfortunately have to consider using a different framework instead of Typebot.
Could you please let me know if there is any realistic timeline or workaround for this?
Can you tell me how you reproduce the bug step by step? 🙏
This is a bug, it does not require a workaround, just a fix, don't worry
I just need more info from your side, all this is very abstract
is there some type of export so u can reproduce it?
Ideally, you would create the most minimal typebot that reproduces the bug then send it as JSON to me and explain how to reproduce the bug 🙏
it is difficult to do, is not a small typebot so i have to do a lot of tests for reproduce that with a minimal chat-bot.
there isn't log o somethings like that in your BE, with my id u can't search in that logs?
u have a 500 internal server error and no logs for that endpoint?
https://app.typebot.io/api/trpc/results.getResultTranscript?input=%7B%22json%22%3A%7B%22typebotId%22%3A%22cmgtedeav0001la04rqje5ao5%22%2C%22resultId%22%3A%22n5kvngrjpg7tlsihbdvdzdyn%22%7D%7D
this is the GET who give 500 internal server error
{
"error": {
"json": {
"message": "Parsed reply is in fail status when computing result transcript",
"code": -32603,
"data": {
"code": "INTERNAL_SERVER_ERROR",
"httpStatus": 500,
"path": "results.getResultTranscript",
"logError": null,
"zodError": null
}
}
}
}
this is the result
u can reproduce in your BE with the GET i give u and search why of this bug
today i have to choose if typebot is ok for us or nothing. So pls help for that bug
or maybe we can do a call so i can stream to you the typebot
Ok will try to investigate today
I managed to reproduce the issue
Implementing a fix now
oh perfect, thank u
dosn't work at all, the problem was fixet for chat like the screenshot but for others like
GET - https://app.typebot.io/api/trpc/results.getResultTranscript?input=%7B%22json%22%3A%7B%22typebotId%22%3A%22cmgtedeav0001la04rqje5ao5%22%2C%22resultId%22%3A%22hbjj51zwtb9qltm4ndo6cfjo%22%7D%7D
i received
{
"json": {
"message": "Parsed reply is in fail status when computing result transcript",
"code": -32603,
"data": {
"code": "INTERNAL_SERVER_ERROR",
"httpStatus": 500,
"path": "results.getResultTranscript",
"logError": null,
"zodError": null
}
}
}
i update the id of the chatbot with telemedicina-chatbot and add just 1 condition block from the one i sent u before, this is the export updated
Did not say the fix was deployed!
I just pushed a potential fix. Try in 15 min 🙏
oh sorry, my bad, I misunderstood
Thank you, everything you did is working perfectly.
Hi,
I’ve found a new bug in the transcription: as you can see from the two screenshots, the transcribed text is not fully consistent with what was actually said.
https://app.typebot.io/api/trpc/results.getResultTranscript?input=%7B%22json%22%3A%7B%22typebotId%22%3A%22cmgtedeav0001la04rqje5ao5%22%2C%22resultId%22%3A%22nmkdad7srsamdzoqirog0bsm%22%7D%7D
Thanks again for your support — I’d be grateful if you could take a look at this new problem too.
the response miss of some steps
Checking now
I understand the issue and implementing a fix, will report back when it's deployed
thank u
Should be deployed
Though won't work for existing result, you'll have to create a new one
Let me know if that fixed it
it's fixed, thank u so much