Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] MongoDB Atlas Chat Memory client closes and breaks flow #3115

Open
jtguzman opened this issue Aug 30, 2024 · 0 comments
Open

[BUG] MongoDB Atlas Chat Memory client closes and breaks flow #3115

jtguzman opened this issue Aug 30, 2024 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@jtguzman
Copy link

Describe the bug
When using the MongoDB Atlas Chat Memory, after some uses the client closes and it does not reconnect. This makes the flow to break with the message "Client must be connected before running operations"
The client reconects if the server is restarted, but after a random time it will close.

To Reproduce
Steps to reproduce the behavior:

  1. Create a flow
  2. Configure a new MongoDB Atlas Chat Memory node
  3. Try the node successfully
  4. Wait some time
  5. Try again until it closes.

Expected behavior
The client should reconnect and the flow should continue without breaking.

Screenshots
image

Flow
Any flow with the node

Setup

  • Installation docker-compose up -d
  • Flowise Version 2.0.5
  • OS: AWS Linux
  • Browser: Edge

Additional context
A lot of problems with MongoDB and the 2.x.x update...

@HenryHengZJ HenryHengZJ added bug Something isn't working enhancement New feature or request labels Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants