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

Changes may be loss if a orchestrate page is opened in multiple browser at the same time #3168

New Issue
Closed
opened 2026-02-21 17:54:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:54:36 -05:00
Owner
Copy Link
Copy Source

Originally created by @cheeman on GitHub (May 10, 2024).

Self Checks

  • 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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

I (Person A) and a colleague (Person B) each have a orchestrate page open on our own browsers, with the current version being v1.

  • After I open it, I make no changes and keep the page open.
  • Then, Person B opens the page, makes modifications, and publishes version v2, then close the editing page.
  • About 15 minutes later, my page triggers an auto-save, and the content version reverts back to v1.

Although the changes have not been published, if they are mistakenly published later, it could lead to unintended confusion.

2. Describe the feature you'd like to see

The auto-save feature should be designed to prevent the saving of outdated versions of a document.
Alternatively, or in addition, a robust version control system that supports collaboration should be implemented. The orchestrate page should allow multiple users to work on a document simultaneously without overwriting each other's changes and provide a clear history of all edits made.

3. How will this feature improve your workflow or experience?

We no longer have to worry about losing changes.

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @cheeman on GitHub (May 10, 2024). ### Self Checks - [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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? I (Person A) and a colleague (Person B) each have a orchestrate page open on our own browsers, with the current version being v1. - After I open it, I make no changes and keep the page open. - Then, Person B opens the page, makes modifications, and publishes version v2, then close the editing page. - About 15 minutes later, my page triggers an auto-save, and the content version reverts back to v1. Although the changes have not been published, if they are mistakenly published later, it could lead to unintended confusion. ### 2. Describe the feature you'd like to see **The auto-save feature should be designed to prevent the saving of outdated versions of a document.** Alternatively, or in addition, a robust version control system that supports collaboration should be implemented. The orchestrate page should allow multiple users to work on a document simultaneously without overwriting each other's changes and provide a clear history of all edits made. ### 3. How will this feature improve your workflow or experience? We no longer have to worry about losing changes. ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 🌊 feat:workflow label 2026-02-21 17:54:36 -05:00
yindo closed this issue 2026-02-21 17:54:36 -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#3168
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?