search

langflow-ai / langflow

Langflow is a low-code app builder for RAG and multi-agent AI applications. It’s Python-based and agnostic to any model, API, or database.
http://www.langflow.org
MIT License
34.39k stars 4.14k forks source link

Langflow tables does not work in "Message history" #4661

Open SavvySupport opened 2 hours ago

SavvySupport commented 2 hours ago

Bug Description

In v1.1, the "message history" component does not work.

In "controls" for the "message history" component.. under external memory.. it says "if empty, it will use Langflow tables."

However, when I run a chat flow with this component connected as we previously did with "chat memory" component, it does not pass any "chat history".

Reproduction

  1. Build a standard chat flow with the following components: chat input, a prompt, message history, an LLM (e.g. openai), and chat output.
  2. Connect "message history" to the "prompt" component (with {chat_history} as a field).
  3. Run the flow.

Expected behavior

Expecting it to operate as "chat memory" component did, and pass chat history to the prompt.

Who can help?

No response

Operating System

MacOS

Langflow Version

1.1

Python Version

3.10

Screenshot

No response

Flow File

No response

SavvySupport commented 2 hours ago
Screenshot 2024-11-18 at 4 26 49 pm

See external memory description.

dosubot[bot] commented 2 hours ago

I found a similar unsolved discussion regarding changes to Langflow, which might be related to the issue you're experiencing. You can check it out here [1].

Regarding your issue, the 'message history' component is supposed to pass chat history to the 'prompt' component by connecting the messages_text output from the 'message history' component to the CHAT_HISTORY input of the 'prompt' component. This setup should allow the chat history to be incorporated into the prompt generation process [2][3].

If the Langflow tables are not working as expected, it might be due to a configuration issue or a bug in the current version. Ensure that the 'message history' component is correctly configured to use Langflow tables when no external memory is specified. If the problem persists, it might be worth checking for any updates or patches that address this issue in version 1.1.

To continue talking to Dosu, mention @dosu.