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

Can't locate tools when importing workflows from dev environment to production environment. #7337

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

Originally created by @yuhua6379 on GitHub (Dec 22, 2024).

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

0.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

BackGround

I have a dev environment that has several custom tools. I import them throught Swagger.
I am sure these tools are imported correctly and work well in both pub and dev env...
The implementions and versions of these tools are same in two envs.
image

Bug

This happends when I am trying to import my workflow to pub env which exports from dev env.
image

Dify can't locate to my tools. And the reason of this is the provider_id is different in two envs.
image

Please help or fix this bug

But I have already kept the account and user name same.
How to make this right when I import my workflows or chatflows.
Please help.

✔️ Expected Behavior

Import my workflow from dev to pub correctly

❌ Actual Behavior

Dify can't locate tools althought the tools are same in two envs.

Originally created by @yuhua6379 on GitHub (Dec 22, 2024). ### 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 0.14.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ### BackGround I have a dev environment that has several custom tools. I import them throught Swagger. I am sure these tools are imported correctly and work well in both pub and dev env... The implementions and versions of these tools are same in two envs. ![image](https://github.com/user-attachments/assets/0bc22aea-2ddf-4951-b46b-cab0e9a31d9a) ### Bug This happends when I am trying to import my workflow to pub env which exports from dev env. ![image](https://github.com/user-attachments/assets/5e4ddc54-9682-42e3-8750-31dbd6cde6cd) Dify can't locate to my tools. And the reason of this is the `provider_id` is different in two envs. ![image](https://github.com/user-attachments/assets/cd966326-e4ba-42bf-af92-cd9659170fca) ### Please help or fix this bug But I have already kept the account and user name same. How to make this right when I import my workflows or chatflows. Please help. ### ✔️ Expected Behavior Import my workflow from dev to pub correctly ### ❌ Actual Behavior Dify can't locate tools althought the tools are same in two envs.
yindo added the 🌊 feat:workflow label 2026-02-21 18:20:04 -05:00
yindo closed this issue 2026-02-21 18:20:04 -05:00
yindo commented 2026-02-21 18:20:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 22, 2024):

Hey @yuhua6379! 👋 I'm here to help you with any bugs, questions, or contributions. Let's squash those pesky bugs together!

To resolve the issue of Dify not locating tools when importing workflows from the development environment to the production environment due to different provider_ids, you can follow these steps:

  1. Ensure Consistent provider_id: When migrating workflows, make sure that the provider_id in the production environment matches the one used in the development environment. This might involve updating the provider_id in the production database to match the development environment.

  2. Modify the Import Process: If the provider_id cannot be the same, modify the import process to update the provider_id in the workflow configuration to match the production environment's provider_id.

  3. Database Synchronization: Ensure that the WorkflowToolProvider entries in the production database are correctly set up with the appropriate provider_id and other related configurations.

The WorkflowToolProviderController class uses the provider_id to fetch tools from the database, which is crucial for locating the correct tools. Therefore, aligning the provider_id between environments or adjusting the import logic to handle different provider_ids is necessary [1].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 22, 2024): <!-- Greeting --> Hey @yuhua6379! 👋 I'm here to help you with any bugs, questions, or contributions. Let's squash those pesky bugs together! <!-- Answer --> To resolve the issue of Dify not locating tools when importing workflows from the development environment to the production environment due to different `provider_id`s, you can follow these steps: 1. **Ensure Consistent `provider_id`:** When migrating workflows, make sure that the `provider_id` in the production environment matches the one used in the development environment. This might involve updating the `provider_id` in the production database to match the development environment. 2. **Modify the Import Process:** If the `provider_id` cannot be the same, modify the import process to update the `provider_id` in the workflow configuration to match the production environment's `provider_id`. 3. **Database Synchronization:** Ensure that the `WorkflowToolProvider` entries in the production database are correctly set up with the appropriate `provider_id` and other related configurations. The `WorkflowToolProviderController` class uses the `provider_id` to fetch tools from the database, which is crucial for locating the correct tools. Therefore, aligning the `provider_id` between environments or adjusting the import logic to handle different `provider_id`s is necessary <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/workflow_tool_provider.py)</sup>. <!-- 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/05f69f43-617a-4b87-a29a-3ef36b315606?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/05f69f43-617a-4b87-a29a-3ef36b315606?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/05f69f43-617a-4b87-a29a-3ef36b315606?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/05f69f43-617a-4b87-a29a-3ef36b315606?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/05f69f43-617a-4b87-a29a-3ef36b315606?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/05f69f43-617a-4b87-a29a-3ef36b315606?feedback_type=other)</sup>
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:workflow
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#7337
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?