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

External data tool not work #868

New Issue
Closed
opened 2026-02-21 17:28:47 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 17:28:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @opsvr on GitHub (Jan 4, 2024).

Originally assigned to: @GarfieldDai on GitHub.

Self Checks

Dify version

0.4.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Adding external_data_tool to the API extension allows you to see the ping request. Adding external_data_tool works normally, but when you create an application and add a tool to it, the tool interface is not called.
1、API External add api；
2、create app；
3、add tools，set ver in prompt；
4、deploy；
5、test；

✔️ Expected Behavior

No response

❌ Actual Behavior

Adding external_data_tool to the API extension allows you to see the ping request. Adding external_data_tool works normally, but when you create an application and add a tool to it, the tool interface is not called.

Originally created by @opsvr on GitHub (Jan 4, 2024). Originally assigned to: @GarfieldDai on GitHub. ### 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 file this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). ### Dify version 0.4.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Adding external_data_tool to the API extension allows you to see the ping request. Adding external_data_tool works normally, but when you create an application and add a tool to it, the tool interface is not called. 1、API External add api； 2、create app； 3、add tools，set ver in prompt； 4、deploy； 5、test； ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior Adding external_data_tool to the API extension allows you to see the ping request. Adding external_data_tool works normally, but when you create an application and add a tool to it, the tool interface is not called.
yindo added the 🐞 bug label 2026-02-21 17:28:47 -05:00
yindo closed this issue 2026-02-21 17:28:47 -05:00
yindo commented 2026-02-21 17:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 4, 2024):

Can you paste the log you sent to the LLM? It's in the log&anno, you can hover the message to view the logs.

@crazywoola commented on GitHub (Jan 4, 2024): Can you paste the log you sent to the LLM? It's in the log&anno, you can hover the message to view the logs.
yindo commented 2026-02-21 17:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@opsvr commented on GitHub (Jan 4, 2024):

I know what the problem is. I created a text generation application, and selecting the dialog type can call the API normally. Why doesn't the text generation application support calling the API? Is it a bug?
@crazywoola

@opsvr commented on GitHub (Jan 4, 2024): I know what the problem is. I created a text generation application, and selecting the dialog type can call the API normally. Why doesn't the text generation application support calling the API? Is it a bug? @crazywoola
yindo commented 2026-02-21 17:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 4, 2024):

Yes, we are working on this.

@crazywoola commented on GitHub (Jan 4, 2024): Yes, we are working on this.
yindo commented 2026-02-21 17:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@canny[bot] commented on GitHub (Jan 4, 2024):

This issue has been linked to a Canny post: API external data extension fails in 0.4.2/0.4.3 🎉

@canny[bot] commented on GitHub (Jan 4, 2024): This issue has been linked to a Canny post: [API external data extension fails in 0.4.2/0.4.3](https://dify.canny.io/admin/board/issue-reports/p/api-external-data-extension-fails-in-042043) :tada:
yindo commented 2026-02-21 17:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@GarfieldDai commented on GitHub (Jan 5, 2024):

@opsvr #1942 Fixed.

@GarfieldDai commented on GitHub (Jan 5, 2024): @opsvr #1942 Fixed.
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 🐞 bug
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#868
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?