What triggers a new page version to be created?
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
It has been observed that certain actions in Confluence will trigger a new page version of the page to be created while other actions do not. This behavior doesn't appear to be consistent.
Diagnosis
Environment
- Confluence Server and Datacenter
- Collaborative Editing is not enabled
Cause
Any current edits to a given page are tracked via Hazelcast and it's record of "Page Edit Heartbeat Activities". When a new content edit is initiated on a page, a heartbeat activity is recorded in the Confluence cache. If someone is editing the page at the moment (browser sent recently editing heartbeat), a new page version is generated. If no one is editing the page currently (no recent heartbeats recorded), the page can be updated without a new page version creation. These rules are in place to prevent overriding of page content by another page editor.