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
When a user sends their first message containing an image in a session, Flowise ignores this image, and responds with "I don't see any image."
Interestingly, if the user continues to send second, third, or subsequent messages with images in the same session, these subsequent image messages are processed correctly.
As for the first ignored image message, Flowise only processes it correctly after the user sends another message (with or without images).
This issue appears to be related to how Flowise handles the first image message in a session, possibly due to asynchronous image processing or session context initialization. I've tried various solutions (including adding delays, ensuring image loading completion, adjusting message history), but the issue persists.
Steps to Reproduce:
Start a new chat session
Send a message with an image
Observe that Flowise responds with "I don't see any image"
Send another message (with or without image)
Observe that Flowise can now see the previous image
Expected Behavior:
The first image message should be processed correctly immediately, just like subsequent image messages.
Current Behavior:
The first image message is ignored until a subsequent message is sent.
All subsequent image messages work correctly on first try.
The text was updated successfully, but these errors were encountered:
Issue with Flowise API handling image messages:
Interestingly, if the user continues to send second, third, or subsequent messages with images in the same session, these subsequent image messages are processed correctly.
As for the first ignored image message, Flowise only processes it correctly after the user sends another message (with or without images).
This issue appears to be related to how Flowise handles the first image message in a session, possibly due to asynchronous image processing or session context initialization. I've tried various solutions (including adding delays, ensuring image loading completion, adjusting message history), but the issue persists.
Steps to Reproduce:
Expected Behavior:
Current Behavior:
The text was updated successfully, but these errors were encountered: