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

Workflow Models Marked as Deprecated After Page Refresh #8638

New Issue
Closed
opened 2026-02-21 18:26:47 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:26:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @Tokeii0 on GitHub (Feb 26, 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

0.15.3

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

After each page refresh, all models in the workflow will be marked as deprecated and must be reset to function properly. However, after publishing, this does not affect their usage on a standalone page, but when configuring the workflow again, the models need to be reset to be used.
Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Tokeii0 on GitHub (Feb 26, 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce After each page refresh, all models in the workflow will be marked as deprecated and must be reset to function properly. However, after publishing, this does not affect their usage on a standalone page, but when configuring the workflow again, the models need to be reset to be used. ![Image](https://github.com/user-attachments/assets/5f434d51-1dbd-48fd-838a-98666ad26a62) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:26:47 -05:00
yindo closed this issue 2026-02-21 18:26:47 -05:00
yindo commented 2026-02-21 18:26:48 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 26, 2025):

Hey @Tokeii0! I'm here to help you with bug fixes, answer your questions, and guide you on how to contribute. Let's tackle this issue together!

The issue you're experiencing, where workflow models are marked as deprecated after a page refresh, might be related to the caching mechanism in Dify. Dify uses a caching system in the ApolloClient class and Redis for caching configurations, which could delay the reflection of changes, such as model deprecation status, until the cache is updated [1][2]. Additionally, Dify employs a snapshot system for model configurations in conversations, which might cause existing configurations to persist despite changes [3].

To address this, you might want to check if the cache is being properly updated or if there are any issues with the snapshot system that could be causing the models to appear deprecated after a refresh.

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 (Feb 26, 2025): <!-- Greeting --> Hey @Tokeii0! I'm here to help you with bug fixes, answer your questions, and guide you on how to contribute. Let's tackle this issue together! <!-- Answer --> The issue you're experiencing, where workflow models are marked as deprecated after a page refresh, might be related to the caching mechanism in Dify. Dify uses a caching system in the `ApolloClient` class and Redis for caching configurations, which could delay the reflection of changes, such as model deprecation status, until the cache is updated <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/configs/remote_settings_sources/apollo/client.py)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/model_manager.py)</sup>. Additionally, Dify employs a snapshot system for model configurations in conversations, which might cause existing configurations to persist despite changes <sup>[[3]](https://github.com/langgenius/dify/issues/14095)</sup>. To address this, you might want to check if the cache is being properly updated or if there are any issues with the snapshot system that could be causing the models to appear deprecated after a refresh. <!-- 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/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b194385f-cef1-4b14-969d-5d90b779a136?feedback_type=other)</sup>
yindo commented 2026-02-21 18:26:48 -05:00
Author
Owner
Copy Link
Copy Source

@lxq15123912534 commented on GitHub (Feb 26, 2025):

me too，，seek assist

@lxq15123912534 commented on GitHub (Feb 26, 2025): me too，，seek assist
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#8638
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?