Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
My chatflows used the In Memory Vector Store and everything was fine until I pulled the latest Flowise docker image, after which the vector store just stopped working. The issue was closed in May 2024. A maintainer responded on the thread and the reporter confirmed it was fixed.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This was a regression in the Flowise docker build that broke the In Memory Vector Store. The maintainer pushed the fix in release 1.8.1, so the answer is to upgrade to 1.8.1 or later and pull the new image. The reporter thanked them and confirmed it worked, so theres no config workaround, just the version. Source: https://github.com/FlowiseAI/Flowise/issues/2501
Source: https://github.com/FlowiseAI/Flowise/issues/2501
Shows how to fix flowise In Memory Vector Store not working after docker image update. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes snyk container scans that cannot pull an image your docker login can.
Shows how to fix agent Flow v1 fails after upgrading to Flowise v3: langChainTracer.convertToRunTree is not a function. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.