langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-26 18:36:52 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Issue Title: Contextual Conflict When Switching Models Based on Parameter Judgment in the Same Workflow #10595

New Issue
Closed
opened 2026-02-21 18:48:49 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:48:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @lbl1120 on GitHub (Mar 12, 2025).

Originally assigned to: @crazywoola on GitHub.

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.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

In the same conversational workflow, a parameter is passed to control whether deep thinking is enabled. Within the workflow nodes, the parameter is evaluated to switch between different models for responses. When deep thinking is not enabled initially, the Qwen model (without deep thinking) is used. However, when the parameter is switched to enable deep thinking within the same session, the workflow switches to the DeepSeek model accordingly. The issue is that the responses from DeepSeek do not reflect deep thinking as expected.

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @lbl1120 on GitHub (Mar 12, 2025). Originally assigned to: @crazywoola on GitHub. ### 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.1 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce In the same conversational workflow, a parameter is passed to control whether deep thinking is enabled. Within the workflow nodes, the parameter is evaluated to switch between different models for responses. When deep thinking is not enabled initially, the Qwen model (without deep thinking) is used. However, when the parameter is switched to enable deep thinking within the same session, the workflow switches to the DeepSeek model accordingly. The issue is that the responses from DeepSeek do not reflect deep thinking as expected. ![Image](https://github.com/user-attachments/assets/fd838731-7d4c-4dcb-93ea-ff63735137aa) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🌊 feat:workflow label 2026-02-21 18:48:49 -05:00
yindo closed this issue 2026-02-21 18:48:49 -05:00
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#10595
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?