Live edits may not update public content

Publishing a space should automatically lock live edits, and we are rolling out a script that will auto-lock existing published content. If you would like to manually address this in the meantime, you can lock live edits for any spaces you wish to protect: https://docs.gitbook.com/editing-content/editing-pages/live-edits-and-real-time-collaboration#toggling-live-edit-on-or-off

We are about to lock live edits by default on all public spaces. You can still edit your content using change requests.

This is related to our caching related incident, but we still wanted to share the details separately. If live edits in a public space do get published, you may be able to work around it by locking edits and switching to using change requests. Please check https://docs.gitbook.com/editing-content/editing-pages/live-edits-and-real-time-collaboration#toggling-live-edit-on-or-off & https://docs.gitbook.com/editing-content/editing-pages/change-requests