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

[ufo009e]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [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?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

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}

[crazywoola]

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.

[avataar]

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:

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

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

[ufo009e]

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.

[xhuanlee]

is there any way to fix this?

[perzeuss]

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

[winnersoftmanager]

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

[meteorjim]

same issue here

[Hanxiao-Adam-Qi]

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!