langgenius / langgenius/dify

[Agent] Respond node can't get output from agent node with Function Calling policy

Open
#38,360 1 comment 1 reaction 0 assignees View on GitHub
🐞 bug 1.15.0 project#dify
Dominant language
TypeScript
Stars
156k
Forks
24.6k
Avg merge
22h 9m
Merged PRs (30d)
610

Description

### Self Checks

- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
- [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.
- [x] I confirm that I am using English to submit this report, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.

### Dify version

v1.15.0

### Cloud or Self Hosted

Self Hosted (Docker)

### Steps to reproduce

As shown figure, just configure the agent node with func call, but the response node can't get output from the agent

- Function Calling with Thinking mode on
Image

But the weird case is, if I disable the thinking mode, the response node can get output from the agent

- Function Calling with Thinking mode off
Image

Another bug is, the variable from agent was duplicated
Image

### ✔️ Expected Behavior

Get response

### ❌ Actual Behavior

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue on Dify v1.15.0 in a self-hosted Docker setup with an Agent node using Function Calling and Thinking mode enabled. Compare the response-node output and agent variable values with Thinking mode disabled; done means the response is returned and the agent variable is no longer duplicated.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.