Skip to main content
​
2026-07-08
v0.1.8: Large collection graph fix

​
Fixed: 500 error on large collections

GET /api/v1/collections/{id}/graph could return a 500 error for collections with a few hundred or more claims/predictions/entities combined. Fetching a new collection’s graph for the first time after it grew past this size would fail entirely.Ingesting a new source into an already-large collection could also fail for the same underlying reason, blocking further ingestion into that collection.

​
What changed

Internal lookups that resolve node titles now run as a single server-side query instead of passing large ID lists in the request. This removes the size ceiling — collections with any number of nodes now work the same way.No response shape changed; if you were affected by this, requests that previously failed now simply succeed.