Is this a bug? Session id Memory

[toi500]

I notice that when you set up a Session id for a Memory Module, lets say Session Id=Test, it only works from the UI Source:

--

--

But if you try the same chatbot from the API/EMBED source, the Session id is random.

--

--

If this is not a bug, what is the point to set up a custom Session id?

It would be very useful if the bot is only being used for 1 user, so they have all the data grouped.

[saatchi-david]

@toi500 I'm experiencing the same when setting a session ID in the Zep memory node. I also expected the set ID to be used everywhere.

[toi500]

@saatchi-david

Apparently it is a thing for all memory nodes. I got this issue with the Zep memory node too and then I tried the Upstash one with the same results.

[HenryHengZJ]

I just tried it seems to work.. I have set a session ID on the memory node:

I then make a call to the API:

I can see the session ID in View Messages:

[toi500]

@HenryHengZJ

Please try to inject the embed script of your testing chatflow to a html file and test it from the font end, that is how I reproduce the bug. I got my flowise instance on Railway, but i dont think this is relevant.

Just tested and got the same buggy results than before. Please check the id:

I also get it right via postman

[HenryHengZJ]

What does your embedded script looks like? @toi500

[toi500]

[HenryHengZJ]

@toi500 for a workaround, since you have hard-coded the sessionId on the UI, you can also do so in the embed script:

<script type="module">
    import Chatbot from 'https://cdn.jsdelivr.net/npm/flowise-embed/dist/web.js';
    Chatbot.init({
        chatflowid: '80612c28-aae1-446d-8d73-58dfd998d565',
        apiHost: 'http://localhost:3000',
        chatflowConfig: {
            sessionId: "abcde"
        }
    });
  </script>

[toi500]

It worked. Thank you for that, I really appreciate it.

So, is this sort of buggy or we do need to overwrite the session id via the embed script too?

[HenryHengZJ]

This is the current design, you'll have to provide sessionId in the chatflow config for embedded, hard coded sessionId is meant for user to test it on UI

[toi500]

Makes sense. Thank you for the clarification, I really appreciate it.