langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

agent to invoke tools #8883

New Issue
Closed
opened 2026-02-21 18:28:22 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:28:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @Aoaoao7 on GitHub (Mar 2, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When I use an agent to invoke tools (which are workflows), and call the agent via an API, the agent invokes the tool (workflow). However, due to the slow response of the workflow, the agent remains in a blocked state. Could future modifications be made to add configurations for the tool? For example, when the agent invokes the workflow tool, the nodes within the workflow could stream responses back to me incrementally, while still allowing the option for blocking responses if needed.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Aoaoao7 on GitHub (Mar 2, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. When I use an agent to invoke tools (which are workflows), and call the agent via an API, the agent invokes the tool (workflow). However, due to the slow response of the workflow, the agent remains in a blocked state. Could future modifications be made to add configurations for the tool? For example, when the agent invokes the workflow tool, the nodes within the workflow could stream responses back to me incrementally, while still allowing the option for blocking responses if needed. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🤖 feat:agent🔨 feat:tools labels 2026-02-21 18:28:22 -05:00
yindo closed this issue 2026-02-21 18:28:22 -05:00
yindo commented 2026-02-21 18:28:22 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 3, 2025):

Hi, @Aoaoao7. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • You reported an issue with agents being blocked by slow responses when invoking tools via an API.
  • Proposed solution: Add configurations for incremental streaming of responses from workflow nodes.
  • No further comments or developments have been made on this issue.

Next Steps

  • Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting here.
  • If there are no updates, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Apr 3, 2025): Hi, @Aoaoao7. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - You reported an issue with agents being blocked by slow responses when invoking tools via an API. - Proposed solution: Add configurations for incremental streaming of responses from workflow nodes. - No further comments or developments have been made on this issue. **Next Steps** - Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting here. - If there are no updates, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🔨 feat:tools 🤖 feat:agent
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: langgenius/dify#8883
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?