Problem

When updating a Confluence page with identical information, whether through the API or the UI, a new version is not created and nothing indicates it. This occurs in the following scenarios:

• Through UI: When editing and publishing a page without making any changes, no new version is recorded.
• Through API: If a PUT request is sent with the same payload and incremented version number, and the content remains unchanged, the operation fails silently with no new version created.

Suggested Solution

Introduce an indicator or notification that alerts users when an update does not result in a new version due to the absence of changes.

Why This Is Important

Having an efficient version history is crucial, especially when using bulk tools or updating pages in loops. Situations like this can disrupt workflow logic without providing any indication of what occurred, making it difficult to troubleshoot.

Workaround

• Through API: You can add a different comment along with the version update to ensure a new version is created in the history.
• Through UI: Modify an aspect of the page content, such as the title or body, to trigger a new version creation.