## TL;DR

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. A maintainer responded on the thread and the reporter confirmed it was fixed.

## Steps

1. 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.

2. What actually fixes it (verified in the thread):

3. 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.

## When to use

You are seeing this: The situation: 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. Use this skill when you run into "Flowise In Memory Vector Store not working after docker image update".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: 1.8.1. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.