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

After upraded to 1.0.0, previous configured customer API tool shows removed and disabled in agent config. #8840

New Issue
Closed
opened 2026-02-21 18:28:04 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 18:28:04 -05:00
Owner
Copy Link
Copy Source

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

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Before upgraded to 1.0.0, I configured some customer tool with openapi schema and they were working fine. After upgraded to 1.0.0 those tools shows removed and disabled. But when I try my agent, it still use that tool and give expected result as before.

What should be the expected behavior for such customer openapi tool created before upgrading?

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @ufo009e on GitHub (Mar 2, 2025). ### Self Checks - [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 (我已阅读并同意 [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. ### Dify version 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Before upgraded to 1.0.0, I configured some customer tool with openapi schema and they were working fine. After upgraded to 1.0.0 those tools shows removed and disabled. But when I try my agent, it still use that tool and give expected result as before. What should be the expected behavior for such customer openapi tool created before upgrading? ![Image](https://github.com/user-attachments/assets/b4f22274-1c04-4be0-a446-22cb09cf62fe) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:28:04 -05:00
yindo closed this issue 2026-02-21 18:28:04 -05:00
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 2, 2025):

The issue you're experiencing with custom API tools appearing as removed or disabled in the agent configuration after upgrading to version 1.0.0 might be related to changes in how Dify handles tool configurations. Although the tools appear disabled, they still function as expected, which suggests a possible UI or configuration display issue.

To address this, you can follow the migration steps outlined in the Dify documentation to ensure that your configurations are correctly migrated and displayed. The migration process involves backing up your data, upgrading the Dify version, and migrating tools to plugins. You can find detailed instructions in the migration guide here: migrate-to-v1.md [1].

If the issue persists after following the migration steps, it might be helpful to check for any updates or patches that address UI-related issues in version 1.0.0.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 2, 2025): <!-- Answer --> The issue you're experiencing with custom API tools appearing as removed or disabled in the agent configuration after upgrading to version 1.0.0 might be related to changes in how Dify handles tool configurations. Although the tools appear disabled, they still function as expected, which suggests a possible UI or configuration display issue. To address this, you can follow the migration steps outlined in the Dify documentation to ensure that your configurations are correctly migrated and displayed. The migration process involves backing up your data, upgrading the Dify version, and migrating tools to plugins. You can find detailed instructions in the migration guide here: [migrate-to-v1.md](https://github.com/langgenius/dify-docs/blob/main/en/development/migration/migrate-to-v1.md) <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/development/migration/migrate-to-v1.md)</sup>. If the issue persists after following the migration steps, it might be helpful to check for any updates or patches that address UI-related issues in version 1.0.0. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/641b2c1f-4481-455d-9af2-076710e0da80?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 2, 2025):

I am not sure if you have read this https://docs.dify.ai/development/migration/migrate-to-v1.
You can try the command in this article.

@crazywoola commented on GitHub (Mar 2, 2025): I am not sure if you have read this https://docs.dify.ai/development/migration/migrate-to-v1. You can try the command in this article.
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@avataar commented on GitHub (Mar 3, 2025):

I see the exact same issue with a freshly installed 1.0.0 with Docker (not upgrading) when I create new agents with custom tools. Just after adding the custom tools it looks like this:

Image

When go to another screen and then back to Studio and the same agent it changes to:

Image

In both cases the tools work, the model is able to call them.

@avataar commented on GitHub (Mar 3, 2025): I see the exact same issue with a freshly installed 1.0.0 with Docker (not upgrading) when I create new agents with custom tools. Just after adding the custom tools it looks like this: <img width="564" alt="Image" src="https://github.com/user-attachments/assets/9d926e5d-50c2-4052-b4dd-c3350b9bdeea" /> When go to another screen and then back to Studio and the same agent it changes to: <img width="549" alt="Image" src="https://github.com/user-attachments/assets/92898140-f977-4d36-b944-db66863c259f" /> In both cases the tools work, the model is able to call them.
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@ufo009e commented on GitHub (Mar 4, 2025):

I am not sure if you have read this https://docs.dify.ai/development/migration/migrate-to-v1. You can try the command in this article.

I followed this step to upgrade the version before open this issue.

@ufo009e commented on GitHub (Mar 4, 2025): > I am not sure if you have read this https://docs.dify.ai/development/migration/migrate-to-v1. You can try the command in this article. I followed this step to upgrade the version before open this issue.
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@xhuanlee commented on GitHub (Mar 5, 2025):

is there any way to fix this?

@xhuanlee commented on GitHub (Mar 5, 2025): is there any way to fix this?
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@perzeuss commented on GitHub (Mar 5, 2025):

I can reproduce this in Dify cloud by:

  1. Creating an agent
  2. creating a custom tool
  3. adding the custom tool to the agent and publish
  4. custom tool is now in disabled state, showing the "tool removed" warning icon
@perzeuss commented on GitHub (Mar 5, 2025): I can reproduce this in Dify cloud by: 1. Creating an agent 2. creating a custom tool 3. adding the custom tool to the agent and publish 4. custom tool is now in disabled state, showing the "tool removed" warning icon
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@winnersoftmanager commented on GitHub (Mar 5, 2025):

I can reproduce this in Dify cloud by:

  1. Creating an agent
  2. creating a custom tool
  3. adding the custom tool to the agent and publish
  4. custom tool is now in disabled state, showing the "tool removed" warning icon

This is the video for your simulation, it's the same behavior in cloud 1.0.0 and my own docker 1.0.0
https://github.com/user-attachments/assets/8c95ddb7-1385-4fd6-9aed-51b1aafe20a0

@winnersoftmanager commented on GitHub (Mar 5, 2025): > I can reproduce this in Dify cloud by: > > 1. Creating an agent > 2. creating a custom tool > 3. adding the custom tool to the agent and publish > 4. custom tool is now in disabled state, showing the "tool removed" warning icon This is the video for your simulation, it's the same behavior in cloud 1.0.0 and my own docker 1.0.0 https://github.com/user-attachments/assets/8c95ddb7-1385-4fd6-9aed-51b1aafe20a0
yindo commented 2026-02-21 18:28:05 -05:00
Author
Owner
Copy Link
Copy Source

@meteorjim commented on GitHub (Mar 6, 2025):

same issue here

@meteorjim commented on GitHub (Mar 6, 2025): same issue here
yindo commented 2026-02-21 18:28:06 -05:00
Author
Owner
Copy Link
Copy Source

@Hanxiao-Adam-Qi commented on GitHub (Mar 7, 2025):

same issue +1

It seems there's a check when loading the tool in agent. Might be somehting like checking if the "plugin" is installed. Since out custom tool is defined in Dify and never actually "installed", so it will be displayed as "removed".

Any quick fix we can do in our end? Or only wait for offical fixing?

Thanks!

@Hanxiao-Adam-Qi commented on GitHub (Mar 7, 2025): same issue +1 It seems there's a check when loading the tool in agent. Might be somehting like checking if the "plugin" is installed. Since out custom tool is defined in Dify and never actually "installed", so it will be displayed as "removed". Any quick fix we can do in our end? Or only wait for offical fixing? Thanks!
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#8840
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?