Chroma "Collection Already Exists" UniqueConstraintError
Workaround available Python, JavaScript, Docker Updated November 15, 2026Based on 2 user reportsHow we research
Quick answer
create_collection fails if the name is taken. Use get_or_create_collection.
Most likely fix: Use get_or_create_collection
How to fix it
Try these in order — the most common fix is first.
1. Use get_or_create_collection
- Replace create_collection(name) with get_or_create_collection(name)
- Or call delete_collection(name) first if you want a clean start
Did this fix it?
Symptoms
UniqueConstraintError: Collection my_collection already exists.
Why it happens
- Script re-run with create_collection
- Persistent data from an earlier run
This guide also covers
- chromadb collection already exists
- UniqueConstraintError chroma
Still not working?
If Chroma keeps failing, you're not alone. See every Chroma problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
Other Chroma errors
- Chroma "Your system has an unsupported version of sqlite3" Error
- Chroma InvalidDimensionException: Embedding Dimension Does Not Match Collection
- Chroma pip install "Failed to build hnswlib" Error
- Chroma Data Disappears After Restart (Persistence Fix)
- Chroma "Collection Not Found" Error
- Chroma "sqlite3.OperationalError: database is locked"
- Chroma "Could not connect to tenant default_tenant" Error
- Chroma "Cannot return the results in a contiguous 2D array. Probably ef or M is too small"