Agent responses are cut off in the chat embed, but i see the full response on voiceflows side.
16 Replies
If you’re seeing the assistant’s full answer inside Voiceflow but the message appears truncated in your embedded chat, it’s almost always a sizing issue with the element you embedded the widget into.
Why it happens
• In
• That element (and any of its parents) becomes the chat’s viewport — if it has a small / fixed height or
• The chat itself scrolls automatically, but it can only scroll inside the space the host element provides. How to fix it
1. Make the host element tall enough or scrollable:
2. OR let the element grow with flex/grid:
3. If you’d rather not manage sizing manually, switch back to the default overlay widget: remove the
https://docs.voiceflow.com/docs/embed-and-customize-styling Once the container can grow/scroll, the full assistant response will be visible in the embedded chat.
Why it happens
• In
render.mode: "embedded" the chat is mounted inside the element you pass in render.target.• That element (and any of its parents) becomes the chat’s viewport — if it has a small / fixed height or
overflow:hidden, anything that exceeds that height is clipped, so the answer looks cut off.• The chat itself scrolls automatically, but it can only scroll inside the space the host element provides. How to fix it
1. Make the host element tall enough or scrollable:
2. OR let the element grow with flex/grid:
3. If you’d rather not manage sizing manually, switch back to the default overlay widget: remove the
render block or set render.mode: 'overlay' – the popup widget handles its own height and long answers will scroll automatically.
4. After changing the page’s CSS, hard-refresh to make sure the latest widget (https://cdn.voiceflow.com/widget/bundle.mjs) is loaded.
Reference docs: Embed and customize styling – “When in render.mode: 'embedded' the chat will mount into the target via Shadow DOM treating the target element as a host.”https://docs.voiceflow.com/docs/embed-and-customize-styling Once the container can grow/scroll, the full assistant response will be visible in the embedded chat.
But the message it happened with was short. Shorter than almost all the other messages @Tico | Voiceflow Assistant
@msampino I got the same problem! I doubt that Ticos answer will solve it. Did you try it?
@msampino @tri55555 i wonder if you are running into the same issue mentioned in https://discord.com/channels/1079548823610871889/1417075179624075304/1417075179624075304
@chirashi it was a rather long message from an agent step:
"Das klingt nach einer echten Meisterleistung – 15 Jahre Verantwortung für die IT-Infrastruktur eines mittelgroßen Unternehmens und dabei stets Lösungen gefunden, auch unter Druck. Das zeigt viel Belastbarkeit und strategisches Denken.\n\nAus der Entfernung betrachtet wirkt das wie ein roter Faden in deiner beruflichen Entwicklung. Damit gibst du schon ein gutes Bild – ich würde gerne noch wissen: Wie bist du als Mensch im Job und was zeichnet dich im Umgang mit anderen aus?"
The part at the end was cut off. : "bist du als Mensch im Job und was zeichnet dich im Umgang mit anderen aus?"
The user continued the conversation by asking if the agent can reformulate the question but without him interfering it would have been stuck.
In another case another user just saw the "typing" effect of the chat for 2-3 minutes until the user refreshed the browser. the logs don't show any problem.
I read your thread but i'm not sure if thats the same problem
Looks like we are having the same problem @tri55555
Looks like the same issue mentioned in that channel as well, but from the looks of it voiceflow is unable to fix it
@msampino @tri55555 you could comment directly in that other thread so the developer knows this is happening to 2 more people too. i think he would value seeing examples of your logs as well
hey guys, is this still happening? I would like to look deeper into this issue, but I haven't been able to reproduce on my side
are you guys using agent steps for the output? specificall when the cut-off happened, was it using a message step, agent step, or something else?
hi @Jayho , indeed it still happens without an obvious reason. On my end it's from an agent output, take a look at the attached.
Thank you
got it thanks for letting me know @Antonis we're looking into it although it is indeed very hard to replicate
@Jayho is there any way i can assist somehow? Maybe sharing my structure/nodes/debug info etc. It's weird as it happens frequently to me i.e. once per 3-4 chats, hence we are re-evaluating if we can eventually keep using it.
@Antonis if u can reproduce it regularly i would love to jump on a call to debug together, feel free to DM me
@Jayho Hey, sorry for not answering. I was on a long trip. How did it work out for you? I can still provide logs or other help if you want.
sorry its been a while, this is related to text streaming getting cut off? is it still occuring?
No not anymore from my side
Got it great, thanks for letting me know