Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4704] [BUG]: Chroma Cloud upsert limitations #2977

New Issue
Closed
opened 2026-02-22 18:32:07 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:32:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @timothycarambat on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4704

How are you running AnythingLLM?

All versions

What happened?

For Chroma Cloud customers, the base offering provides a standard availability tier and quote - however, AnythingLLM's integration is not cognizant of this and will fail with a 422 if upserting many records at once.

Error adding to ChromaDB: Error: Failed to fetch https://api.trychroma.com:8000/api/v2/tenants/****/databases/development/collections/***/add with status 422: Unprocessable Entity

To fix this, we can ensure payloads per-request are within limits/tiers as well as failover with a better error message for 422 payloads, since this can manifest in other ways.

Additionally, cached upserts need to also be aware of this.

Are there known steps to reproduce?

No response

Originally created by @timothycarambat on GitHub (Dec 3, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4704 ### How are you running AnythingLLM? All versions ### What happened? For Chroma Cloud customers, the base offering provides a [standard availability tier and quote](https://docs.trychroma.com/cloud/quotas-limits) - however, AnythingLLM's integration is not cognizant of this and will fail with a 422 if upserting many records at once. ``` Error adding to ChromaDB: Error: Failed to fetch https://api.trychroma.com:8000/api/v2/tenants/****/databases/development/collections/***/add with status 422: Unprocessable Entity ``` To fix this, we can ensure payloads per-request are within limits/tiers as well as failover with a better error message for 422 payloads, since this can manifest in other ways. Additionally, cached upserts need to also be aware of this. ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:32:07 -05:00
yindo closed this issue 2026-02-22 18:32:07 -05:00
yindo changed title from [BUG]: Chroma Cloud upsert limitations to [GH-ISSUE #4704] [BUG]: Chroma Cloud upsert limitations 2026-06-05 14:49:37 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2977
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?