## TL;DR

Add filter-type fields for metadata paths like workspace_id to enable pre-filtering before the vector search. The index name is case-sensitive and must match exactly what the query references.

## Fix

1. Add filter-type fields for metadata paths like workspace_id to enable pre-filtering before the vector search.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this MongoDB Atlas Vector Search feature.
- The symptom matches: index not found is usually a name or status problem.

## When NOT to use

- Unrelated MongoDB Atlas Vector Search issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against MongoDB Atlas Vector Search. Source: https://github.com/cristiantumani/corteza.app/blob/HEAD/setup-vector-search.md.

## Variant phrasings

### index not found is usually a name or status problem

## Why it happens

Empty results or 'Cannot find index' errors almost always trace to the index name, its build status, or the dimension config.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/cristiantumani/corteza.app/blob/HEAD/setup-vector-search.md