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

[cheeman]

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.