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

Upgrading from 1.4 to 1.7.2, the published workflow cannot be used, and plug-in parameters are not passed to the plug-in #16741

New Issue
Closed
opened 2026-02-21 19:27:23 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:27:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @taozuinb on GitHub (Sep 4, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Upgrading from 1.4 tto 1.7.2, the published workflow cannot be used, and plug-in parameters are not passed to the plug-in，the format in storage workflows in version 1.7.2 has changed，Is there a script that can swipe historical data and make it legal?

Image

✔️ Expected Behavior

Historically released chatflows and workflows can be used directly.

❌ Actual Behavior

No response

Originally created by @taozuinb on GitHub (Sep 4, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Upgrading from 1.4 tto 1.7.2, the published workflow cannot be used, and plug-in parameters are not passed to the plug-in，the format in storage workflows in version 1.7.2 has changed，Is there a script that can swipe historical data and make it legal? <img width="1013" height="572" alt="Image" src="https://github.com/user-attachments/assets/d03c2002-6e23-4e2a-916e-af5691b2167c" /> ### ✔️ Expected Behavior Historically released chatflows and workflows can be used directly. ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:27:23 -05:00
yindo closed this issue 2026-02-21 19:27:23 -05:00
yindo commented 2026-02-21 19:27:24 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 4, 2025):

Hi @taozuinb! I'm Dosu and I’m helping the dify team.

This issue is caused by a breaking change in the workflow storage format and plugin parameter schema between Dify 1.4 and 1.7.2. In 1.7.2, plugin/tool nodes expect a new parameter structure, so older workflows can't be used directly and plugin parameters won't be passed correctly. There isn't an official migration script or guide for upgrading historical workflow data to the new format.

The most reliable workaround is to manually delete and recreate any problematic workflow nodes—this ensures parameters and model selection work as expected (source). If you want to script a migration, you'll need to transform each node's parameters to match the new schema. Key files for reference are api/models/workflow.py (workflow storage and serialization), api/core/workflow/entities/workflow_entities.py (node structure), and api/repositories/workflow.py (repository logic). Automated migration is possible by reverse-engineering the new node format and updating historical records accordingly, but this will require custom scripting (source).

Let me know if you need technical pointers for writing a migration script.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 4, 2025): <!-- Greeting --> Hi @taozuinb! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This issue is caused by a breaking change in the workflow storage format and plugin parameter schema between Dify 1.4 and 1.7.2. In 1.7.2, plugin/tool nodes expect a new parameter structure, so older workflows can't be used directly and plugin parameters won't be passed correctly. There isn't an official migration script or guide for upgrading historical workflow data to the new format. The most reliable workaround is to manually delete and recreate any problematic workflow nodes—this ensures parameters and model selection work as expected ([source](https://github.com/langgenius/dify/issues/24069)). If you want to script a migration, you'll need to transform each node's parameters to match the new schema. Key files for reference are `api/models/workflow.py` (workflow storage and serialization), `api/core/workflow/entities/workflow_entities.py` (node structure), and `api/repositories/workflow.py` (repository logic). Automated migration is possible by reverse-engineering the new node format and updating historical records accordingly, but this will require custom scripting ([source](https://github.com/langgenius/dify/blob/fb307ae12896e703acdfa8c58d6298825a6a8203/api/models/workflow.py)). Let me know if you need technical pointers for writing a migration script. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/288d7028-1c0f-4cc7-9d73-4f9fdd6823cb?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/25158)
yindo commented 2026-02-21 19:27:24 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 4, 2025):

Should be fixed in v1.8.1

@crazywoola commented on GitHub (Sep 4, 2025): Should be fixed in v1.8.1
yindo commented 2026-02-21 19:27:24 -05:00
Author
Owner
Copy Link
Copy Source

@taozuinb commented on GitHub (Sep 4, 2025):

I upgraded to v1.8.1, but the plug-ins still cannot be used normally in the old released process

@taozuinb commented on GitHub (Sep 4, 2025): I upgraded to v1.8.1, but the plug-ins still cannot be used normally in the old released process
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#16741
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?