-
-
Notifications
You must be signed in to change notification settings - Fork 23.1k
Description
Describe the bug
When using start → LLM node only, uploading an attachment (including images) from an external client works correctly — the LLM returns a response based on the uploaded file.
However, when the flow is start → Condition Agent → LLM node, uploading only an attachment causes an error, as shown below.
I would like to report this as an issue.
+I also tested this in the Flowise Cloud environment, but the same error occurred.
Error
2025-11-14 01:17:54 [ERROR]: [server]: Error executing node llmAgentflow_0: Error in LLM node: Cannot read properties of undefined (reading 'map')
2025-11-14 01:17:54 [ERROR]: [server]:213b200a-1fb3-4463-9ce4-f501a049b821/72926da8-6241-48d9-9a99-a1bb0f9f1d92/ROOM-1d6d499d-6cc5-48b8-b79d-ab562a2cc3f5-2a5cd0dc Error: Error in LLM node: Cannot read properties of undefined (reading 'map')
Error: Error in LLM node: Cannot read properties of undefined (reading 'map')
at executeAgentFlow (/usr/src/packages/server/dist/utils/buildAgentflow.js:1547:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async utilBuildChatflow (/usr/src/packages/server/dist/utils/buildChatflow.js:810:28)
at async Object.buildChatflow (/usr/src/packages/server/dist/services/predictions/index.js:9:28)
at async createPrediction (/usr/src/packages/server/dist/controllers/predictions/index.js:72:41)
Flow
The image below shows the nodes in Flowise Cloud. The same error occurs even when communicating with an external client via the API. In other words, the issue persists in the latest version as well.
Additionally, if I turn Enable Memory off in the LLM node, it works normally.
Flowise Version
3.0.7, 3.0.10