[BUG] - State Persistence Issue: Message Disappears After Response

[AsharibAli]

In the latest version of Flowise, there is a persistent UI bug affecting message visibility after responses are received.

When a user sends a message (i.e., a request is triggered), the system returns the expected response. However, immediately after the response appears, the messages disappears from the UI, making it impossible to trace what was asked. This breaks the conversational continuity and user experience.

This issue occurs across all of my Flowise projects when used externally (e.g., through flowiseChatEmbed). Interestingly, the same functionality works perfectly within the Flowise instance UI, which indicates the bug may lie either in the embedding script (flowiseChatEmbed) or in the exposed frontend state management.

Please prioritize this bug fix as it significantly affects UX in all embedded deployments.

Additional context
This issue appears to match a similar problem reported here: #4349

@HenryHengZJ

[AsharibAli]

See the attached video for clear understanding of the issue

screen-capture.7.webm

[HenryHengZJ]

okay, for more details, are you running Flowise on docker, git, or npm?

Can you copy paste your flowise embedded code? You can remove sensitive info like ID and URL

[AsharibAli]

I’m using the official Flowise GitHub repo, and I’ve deployed it on Render. I’m embedding the chat using the Flowise Chat Embed via the following CDN.

I'm having the issue here: https://www.asharib.xyz/

Let me know if you need more details!

[HenryHengZJ]

FlowiseAI/FlowiseChatEmbed#299

my bad, it was an oversight from my side!

[HenryHengZJ]

it might takes 1-2 days for CDN to updated, in the meantime you can use a specific version: https://cdn.jsdelivr.net/npm/flowise-embed@3.0.1/dist/web.js

[AsharibAli]

Thank you for fixing the issue asap! @HenryHengZJ ❤️