-
-
Notifications
You must be signed in to change notification settings - Fork 24k
Description
Describe the bug
When using Weaviate as a knowledge base via agentKnowledgeVSEmbeddings in an AgentFlow V2 Agent node, every prediction fails with:
Error in Agent node: Error in similaritySearch
TypeError: Cannot read properties of undefined (reading 'get')
at WeaviateStore.similaritySearchVectorWithScoreAndEmbedding (vectorstores.cjs:263:10)
flowise-components Weaviate.js initializes the Weaviate client using weaviate-ts-client v1.6.0 (v2 API):
const client = weaviate_ts_client_1.default.client({ scheme, host });
This v2 client does not have a collections property. However, @langchain/weaviate was upgraded to 1.0.1 in 3.1.0, which requires the v3 client and calls:
const collection = this.client.collections.get(this.indexName); // ← undefined.get()
The standalone Weaviate vector store node is unaffected — only agentKnowledgeVSEmbeddings in the Agent node triggers this path.
To Reproduce
- Create an AgentFlow V2 chatflow with an Agent node
- Add a self-hosted Weaviate knowledge base via agentKnowledgeVSEmbeddings
- Send any message
- Observe the error in worker logs:
Error invoking tool: Error: Error in similaritySearch TypeError: Cannot read properties of undefined (reading 'get') at WeaviateStore.similaritySearchVectorWithScoreAndEmbedding (.../vectorstores.cjs:263:10)
Expected behavior
The Agent node successfully queries Weaviate via agentKnowledgeVSEmbeddings and returns relevant documents.
Screenshots
No response
Flow
No response
Use Method
Docker
Flowise Version
3.1.0
Operating System
Linux
Browser
Chrome
Additional context
Versions confirmed:
| Package | Version |
|---|---|
flowise |
3.1.0 |
weaviate-ts-client (used by Weaviate.js) |
1.6.0 (v2 API) |
@langchain/weaviate |
1.0.1 (expects v3 client) |
weaviate-client |
3.12.0 (v3, present but unused by Weaviate.js) |
Suggested fix:
- Update
Weaviate.jsinflowise-componentsto useweaviate-clientv3 (connectToCustom) instead ofweaviate-ts-clientv1.6.0 - Or pin
@langchain/weaviateback to a version compatible with the v2 client untilWeaviate.jsis migrated
Workaround: Downgrade to Flowise 3.0.13.
Bug report generated with Claude Sonnet 4.6