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] Document Store [Save Config] button is not working as desired #4243

Open
almirb opened this issue Apr 1, 2025 · 0 comments
Open

[BUG] Document Store [Save Config] button is not working as desired #4243

almirb opened this issue Apr 1, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@almirb
Copy link

almirb commented Apr 1, 2025

Describe the bug
When clicking on [Save Config] button on the "Configure Embeddings, Vector Store and Record Manager" screen, doesn't save things.

To Reproduce

  1. Go to 'Document Store' screen
  2. Create new Document Store
  3. Create a basic loader (can be Text File Document Loader) with some random text
  4. Click on "Process".
  5. Go to 'Upsert All Chunks' screen
  6. Configure Embeddings, Vector Store and Record Manager data
  7. Click on 'Save Config'
  8. Go back to previous screen
  9. Go to 'Upsert All Chunks' screen again

Expected behavior
Al the settings would be there, but the config screen is empty.

Setup

  • Installation: docker
  • Flowise Version: 2.2.7-patch.1.
  • OS: Ubuntu 24.04
  • Browser: Brave (but the API call was also tested with Insomnia)

Additional context

  • I'm sure the browser is firing the /api/v1/document-store/vectorstore/save is being fired.
  • The config is only written when using the 'Upsert' button.
  • After the first 'Upsert', you can change something and 'Save Config'. The changes won't be there when returning to the screen.

One very weird thing that happened twice.....
After upserting the first Document Store, created another one.... went to the steps 1 to 9 above.... when return to 'Upsert All Chunks' I saw all the configs (embedding, vector store....) from my other Document Store! 😢 That makes no sense, but It happened twice.

@HenryHengZJ HenryHengZJ added the bug Something isn't working label Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants