Describe the bug
In Flowise versions 2.1.0 and above, using the chat function causes it to "hang" after inputting a prompt. Despite the chat window freezing, the backend continues to make repetitive API calls, filling the SQLite database with duplicate messages. This behavior is absent in version 2.0.7.
To Reproduce
Steps to reproduce the behavior:
Install Flowise on an Amazon EC2 instance (or local Linux/Windows machine) via Docker, npx flowise start, or pnpm start.
Download and install the "Antonym" template from the Marketplace.
Enter a valid OpenAI API key in the ChatOpenAI Connect Credential dialog.
Type a prompt, such as "big," in the chat window.
Observe that the expected response (e.g., "small" or "little") is not returned, and the chat window hangs.
Check the SQLite database to find repeated messages, indicating ongoing calls despite the chat interface being closed or Flowise restarted.
Expected behavior
The chat should respond with a single antonym, such as "small" or "little," and then stop making additional API calls once the response is returned.
Flowise Version: 2.1.0 (issue present in 2.1.0 and above; no issues in 2.0.7)
OS: Linux, Windows
Browser: Chrome, Safari (issue reproducible across different setups)
Additional context
Through troubleshooting, the root cause appears to be in the commits between checkpoints b02bdc and 1c89a, with the issue emerging between the September 16 and September 17 releases.
Describe the bug
In Flowise versions 2.1.0 and above, using the chat function causes it to "hang" after inputting a prompt. Despite the chat window freezing, the backend continues to make repetitive API calls, filling the SQLite database with duplicate messages. This behavior is absent in version 2.0.7.
To Reproduce
Steps to reproduce the behavior:
npx flowise start
, orpnpm start
.Expected behavior
The chat should respond with a single antonym, such as "small" or "little," and then stop making additional API calls once the response is returned.
Flow
See attached Antonym Chatflow.json
Setup
npx flowise start
,pnpm start
]Additional context
Through troubleshooting, the root cause appears to be in the commits between checkpoints
b02bdc
and1c89a
, with the issue emerging between the September 16 and September 17 releases.