langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Update to 1.4.1 broke Chatflows.... #14216

New Issue
Closed
opened 2026-02-21 19:16:07 -05:00 by yindo · 10 comments
yindo commented 2026-02-21 19:16:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @highhead on GitHub (May 27, 2025).

Originally assigned to: @laipz8200 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.4.1

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Open formerly (until an hour ago) working Chatflow via Link f.e. https://udify.app/chat/bAQUU3JdGGt1xYij
  2. Ask a question and hope for an answer

✔️ Expected Behavior

There should be an answer created.

❌ Actual Behavior

No Answer is created, its broken for all chatflows, that worked fine an hour ago.

Image

Additional info:
Normal "Chatbot" still works in this second but all chatflows are broken.

Originally created by @highhead on GitHub (May 27, 2025). Originally assigned to: @laipz8200 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.4.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. Open formerly (until an hour ago) working Chatflow via Link f.e. https://udify.app/chat/bAQUU3JdGGt1xYij 2. Ask a question and hope for an answer ### ✔️ Expected Behavior There should be an answer created. ### ❌ Actual Behavior No Answer is created, its broken for all chatflows, that worked fine an hour ago. ![Image](https://github.com/user-attachments/assets/917dd3eb-79e9-4c07-b012-4b6c799ee27d) Additional info: Normal "Chatbot" still works in this second but all chatflows are broken.
yindo added the 🐞 bugcloud labels 2026-02-21 19:16:07 -05:00
yindo closed this issue 2026-02-21 19:16:08 -05:00
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (May 27, 2025):

Hi @highhead, could you share your DSL file with us to reproduce this issue?

@laipz8200 commented on GitHub (May 27, 2025): Hi @highhead, could you share your DSL file with us to reproduce this issue?
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

PS: Preview in Orchestrate still seems to works...

@highhead commented on GitHub (May 27, 2025): PS: Preview in Orchestrate still seems to works...
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

Using DIFY Cloud option, with the link above being productive. Has worked until not even an hour ago... Cannot upload the yml file here, filetype is not allowed :(

@highhead commented on GitHub (May 27, 2025): Using DIFY Cloud option, with the link above being productive. Has worked until not even an hour ago... Cannot upload the yml file here, filetype is not allowed :(
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

As its happening for all Chatflows and they are not very complex it should easily be reproducable, heres a screenshot....

Image

@highhead commented on GitHub (May 27, 2025): As its happening for all Chatflows and they are not very complex it should easily be reproducable, heres a screenshot.... ![Image](https://github.com/user-attachments/assets/c9ad0622-06b8-4e38-b43a-a0dc7843acaf)
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

IS24 AI Assistant (Chatflow Claude).txt

heres the yml file renamed to .txt and its fine in the Preview, only not via the production link (f.e. https://udify.app/chat/bAQUU3JdGGt1xYij)

@highhead commented on GitHub (May 27, 2025): [IS24 AI Assistant (Chatflow Claude).txt](https://github.com/user-attachments/files/20454177/IS24.AI.Assistant.Chatflow.Claude.txt) heres the yml file renamed to .txt and its fine in the Preview, only not via the production link (f.e. https://udify.app/chat/bAQUU3JdGGt1xYij)
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 27, 2025):

After searching the available documentation, release notes, issues, and codebase for Dify version 1.4.1, I was unable to find any official documentation or prior issues specifically mentioning changes that would break Chatflows in this version.

From the codebase, the core chat interaction logic is managed by the useChat hook, with the handleSend function responsible for sending queries and processing responses, and updateCurrentQAOnTree updating the chat tree with new questions and answers. These components are central to Chatflows functioning as expected, but there is no clear indication of a recent change in 1.4.1 that would explain a complete breakage of all Chatflows while normal chatbot functionality remains intact [source].

No similar issues or discussions were found in the repository, suggesting this may be a new or isolated problem.

At this time, I do not have enough information to identify the exact cause or a specific workaround for the Chatflows issue in 1.4.1. If you have access to error logs or browser console output when attempting to use a Chatflow, sharing those details may help narrow down the root cause. If this is affecting production use, you may want to monitor the repository for updates or fixes related to Chatflows in upcoming releases.

To reply, just mention my name @dosu.

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

@dosubot[bot] commented on GitHub (May 27, 2025): <!-- Answer --> After searching the available documentation, release notes, issues, and codebase for Dify version 1.4.1, I was unable to find any official documentation or prior issues specifically mentioning changes that would break Chatflows in this version. From the codebase, the core chat interaction logic is managed by the `useChat` hook, with the `handleSend` function responsible for sending queries and processing responses, and `updateCurrentQAOnTree` updating the chat tree with new questions and answers. These components are central to Chatflows functioning as expected, but there is no clear indication of a recent change in 1.4.1 that would explain a complete breakage of all Chatflows while normal chatbot functionality remains intact [[source]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/panel/debug-and-preview/hooks.ts). No similar issues or discussions were found in the repository, suggesting this may be a new or isolated problem. At this time, I do not have enough information to identify the exact cause or a specific workaround for the Chatflows issue in 1.4.1. If you have access to error logs or browser console output when attempting to use a Chatflow, sharing those details may help narrow down the root cause. If this is affecting production use, you may want to monitor the repository for updates or fixes related to Chatflows in upcoming releases. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/fa7725cf-faa7-4e0a-9ce9-b943fd381aef?feedback_type=other)</sup>&nbsp;&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/20299)
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

Also tried on a different device (mobile iOS / Safari) with a different network, same issue.

@highhead commented on GitHub (May 27, 2025): Also tried on a different device (mobile iOS / Safari) with a different network, same issue.
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

Seems like you managed to fix it (it actually works again).
I'd really like to know what happened and how this could be avoided in the future, since also our customers were affected.

@highhead commented on GitHub (May 27, 2025): Seems like you managed to fix it (it actually works again). I'd really like to know what happened and how this could be avoided in the future, since also our customers were affected.
yindo commented 2026-02-21 19:16:08 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (May 27, 2025):

Seems like you managed to fix it (it actually works again). I'd really like to know what happened and how this could be avoided in the future, since also our customers were affected.

We're truly sorry for any inconvenience this may have caused. This issue was due to a network interruption during our update, but we've now fixed the issue.

@laipz8200 commented on GitHub (May 27, 2025): > Seems like you managed to fix it (it actually works again). I'd really like to know what happened and how this could be avoided in the future, since also our customers were affected. We're truly sorry for any inconvenience this may have caused. This issue was due to a network interruption during our update, but we've now fixed the issue.
yindo commented 2026-02-21 19:16:09 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (May 27, 2025):

Thanks a bunch for the information!

@highhead commented on GitHub (May 27, 2025): Thanks a bunch for the information!
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 cloud 🐞 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#14216
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?