Qdrant "Not found: Collection doesn't exist" Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Check what exists on this server

   Copy steps
   1. Call client.get_collections() or GET /collections
   2. Compare the exact name, including case
   Did this fix it? Yes No

2. 2. Create the collection first

   Copy steps
   1. Call create_collection with the correct vector size and distance before upserting
   2. With LangChain or LlamaIndex, create the collection manually if the integration does not
   Did this fix it? Yes No

3. 3. Make storage persistent

   Copy steps
   1. Mount a volume: -v $(pwd)/qdrant_storage:/qdrant/storage
   2. Verify the URL and API key point to the intended instance
   Did this fix it? Yes No

Symptoms

Requests return 404: "Not found: Collection `name` doesn't exist!"

Why it happens

• Collection never created (no auto-create)
• Typo or different name between indexing and query code
• App pointed at a different Qdrant instance or cluster than where you created it
• Docker volume not mounted so data vanished after restart
• Collection deleted or recreated

This guide also covers

• qdrant collection not found
• qdrant collection doesn't exist
• qdrant not found collection 404

The same problem in other apps

All not loading, error messages & connection guides →

• Pinecone 429 Too Many Requests Error (Pinecone)
• Weaviate Error: Vector Lengths Don't Match (Weaviate)
• Milvus "collection not loaded" Error (Milvus)
• Chroma "Your system has an unsupported version of sqlite3" Error (Chroma)

Other Qdrant errors

• Qdrant "Wrong input: Vector dimension error: expected dim, got"
• Qdrant Connection Refused (localhost:6333 / Docker)
• Qdrant Out of Memory (OOMKilled / High RAM Usage)
• Why Is Qdrant Search Slow? HNSW, Quantization and Segment Settings
• Qdrant Free Cluster Suspended or Deleted After Inactivity
• Qdrant Snapshot Restore Failed
• How to Cancel Qdrant Cloud and Delete a Cluster