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

Chat Functionality Issue on Dify Workflow Website After Publishing: Refresh Required After First Interaction to Resume Operations #13899

New Issue
Closed
opened 2026-02-21 19:14:25 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 19:14:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaolvtongxue-zt on GitHub (May 15, 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

1.2.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After the workflow designed in Dify clicks publish and goes to a running website, after the first time the chat is sent, the page can't even be clicked and entered a second time, and the page must be refreshed a bit to continue.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @xiaolvtongxue-zt on GitHub (May 15, 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 1.2.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After the workflow designed in Dify clicks publish and goes to a running website, after the first time the chat is sent, the page can't even be clicked and entered a second time, and the page must be refreshed a bit to continue. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:14:25 -05:00
yindo commented 2026-02-21 19:14:25 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 15, 2025):

Please provide some screenshots or recordings, it's hard to guess what's happening here.

@crazywoola commented on GitHub (May 15, 2025): Please provide some screenshots or recordings, it's hard to guess what's happening here.
yindo commented 2026-02-21 19:14:26 -05:00
Author
Owner
Copy Link
Copy Source

@xiaolvtongxue-zt commented on GitHub (May 15, 2025):

Please provide some screenshots or recordings, it's hard to guess what's happening here.请提供一些屏幕截图或录音，很难猜出这里发生了什么。

Buttons are clickable during the first round of AI answers.
At the end of the first round of AI answers, all buttons are all unclickable, including the chat box.
At the same time, the data in EDIT is empty.
After refreshing the page, you can continue chatting.

Image

After refreshing：
Image

@xiaolvtongxue-zt commented on GitHub (May 15, 2025): > Please provide some screenshots or recordings, it's hard to guess what's happening here.请提供一些屏幕截图或录音，很难猜出这里发生了什么。 Buttons are clickable during the first round of AI answers. At the end of the first round of AI answers, all buttons are all unclickable, including the chat box. At the same time, the data in EDIT is empty. After refreshing the page, you can continue chatting. ![Image](https://github.com/user-attachments/assets/022a12fe-3b1e-4e88-b39b-333e9c728766) After refreshing： ![Image](https://github.com/user-attachments/assets/dffb9224-d325-4a5d-9110-0dfb15a99bbd)
yindo commented 2026-02-21 19:14:26 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 15, 2025):

I can not reproduce this in latest branch, maybe you can upgrade dify later.

Image
@crazywoola commented on GitHub (May 15, 2025): I can not reproduce this in latest branch, maybe you can upgrade dify later. <img width="1355" alt="Image" src="https://github.com/user-attachments/assets/bfa57d2c-41ab-4d6d-853d-3f0b89a3a5d7" />
yindo commented 2026-02-21 19:14:26 -05:00
Author
Owner
Copy Link
Copy Source

@xiaolvtongxue-zt commented on GitHub (May 15, 2025):

I can not reproduce this in latest branch, maybe you can upgrade dify later.我无法在 latest 分支中重现这一点，也许您可以稍后升级 dify。

Image

If I deploy with docker, can I just pull the new version without affecting the original settings and data? This is one of my concerns.

@xiaolvtongxue-zt commented on GitHub (May 15, 2025): > I can not reproduce this in latest branch, maybe you can upgrade dify later.我无法在 latest 分支中重现这一点，也许您可以稍后升级 dify。 > > <img alt="Image" width="1355" src="https://private-user-images.githubusercontent.com/100913391/443990495-bfa57d2c-41ab-4d6d-853d-3f0b89a3a5d7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDcyOTUwNTUsIm5iZiI6MTc0NzI5NDc1NSwicGF0aCI6Ii8xMDA5MTMzOTEvNDQzOTkwNDk1LWJmYTU3ZDJjLTQxYWItNGQ2ZC04NTNkLTNmMGI4OWEzYTVkNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwNTE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDUxNVQwNzM5MTVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kMzUyNWYzZmQ1MjM0MzFiYjNkMDZiODMzNWJjNzEzOTE5MGNmNzlmMjFiNmZlODZiNzdlOTQ1MWVlZTg3OWM4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.ePq7Bkzx0tpDmbXI8GQtLKP0qI0Nf74-Q9zcgChVf8o"> If I deploy with docker, can I just pull the new version without affecting the original settings and data? This is one of my concerns.
yindo commented 2026-02-21 19:14:26 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 15, 2025):

If I deploy with docker, can I just pull the new version without affecting the original settings and data? This is one of my concerns.

Please follow the release log carefully. You might need to adjust the .env with the new .env.example if necessary. This is important, besides that you should upgrade to the latest version without any problems.

@crazywoola commented on GitHub (May 15, 2025): > If I deploy with docker, can I just pull the new version without affecting the original settings and data? This is one of my concerns. Please follow the release log carefully. You might need to adjust the `.env` with the new `.env.example` if necessary. This is important, besides that you should upgrade to the latest version without any problems.
yindo commented 2026-02-21 19:14:26 -05:00
Author
Owner
Copy Link
Copy Source

@xiaolvtongxue-zt commented on GitHub (May 15, 2025):

If I deploy with docker, can I just pull the new version without affecting the original settings and data? This is one of my concerns.

Please follow the release log carefully. You might need to adjust the .env with the new .env.example if necessary. This is important, besides that you should upgrade to the latest version without any problems.

Thank you~!

@xiaolvtongxue-zt commented on GitHub (May 15, 2025): > > If I deploy with docker, can I just pull the new version without affecting the original settings and data? This is one of my concerns. > > Please follow the release log carefully. You might need to adjust the `.env` with the new `.env.example` if necessary. This is important, besides that you should upgrade to the latest version without any problems. Thank you~!
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
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#13899
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?