You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since last update 1.8.3 A pending llm response (no timeout) brakes the chatflow
To Reproduce
Steps to reproduce the behavior:
A created a chatflow, in work in progress state, with some queries staying in pending state because I forgot to setup a timeout.
I shared the chatflow and some queries were made provoking a pending response. After what my chatflow becomes impossible to repair.
I tried to restart my container, I changed many parts of my flow etc. The only solution is to start over from scratch.
Setup
Installation Azure container
Flowise Version [e.g. 1.3.8]
OS: [e.g., Linux]
Browser [e.g. chrome, edge... ]
Additional context
My chatflow was working with 1.8.2. The pending queries didn't blocked everything. Sory for my poor explanation, I'm not a programmer.
Tks if you have any advices. (I did activate timeout now)
The text was updated successfully, but these errors were encountered:
Gallisatyricon
changed the title
[BUG]
[BUG]Since last update 1.8.3 A pending llm response (no timeout) brakes the chatflow
Jun 27, 2024
After several tests, I figure out that this occurs only when ChatGPT4o is used in AzureOpenAI chat module. Switching back to ChatGPT4turbo stop creating these infinite pending loops.
Describe the bug
Since last update 1.8.3 A pending llm response (no timeout) brakes the chatflow
To Reproduce
Steps to reproduce the behavior:
A created a chatflow, in work in progress state, with some queries staying in pending state because I forgot to setup a timeout.
I shared the chatflow and some queries were made provoking a pending response. After what my chatflow becomes impossible to repair.
I tried to restart my container, I changed many parts of my flow etc. The only solution is to start over from scratch.
Setup
Additional context
My chatflow was working with 1.8.2. The pending queries didn't blocked everything. Sory for my poor explanation, I'm not a programmer.
Tks if you have any advices. (I did activate timeout now)
The text was updated successfully, but these errors were encountered: