Issue Summary

When updating a page via the Confluence REST API multiple times (e.g., twice in quick succession with version increments), the draft content is unexpectedly lost, even though the page status is set to "current" and the version is correctly incremented. This results in data loss for customers who rely on drafts to preserve their page edits before publishing.

This is reproducible

Steps to Reproduce

1. Make an initial PUT request to update a page with a version increment (e.g., version 2).

PUT https://<INSTANCE_NAME>.atlassian.net/wiki/api/v2/pages/189693976
{
    "id": "189693976",
    "status": "current",
    "title": "page edit test",
    "body": {
        "representation": "storage",
        "value": "this is a page edit (vers 2)"
    },
    "version": {
        "number": 2,
        "message": "page edited v2"
    }
}
 

    2.  Make a second PUT request to update the same page, incrementing the version to the next number (e.g., version 3).

PUT https://<INSTANCE_NAME>.atlassian.net/wiki/api/v2/pages/189693976
{
    "id": "189693976",
    "status": "current",
    "title": "page edit test",
    "body": {
        "representation": "storage",
        "value": "this is a page edit (vers 3)"
    },
    "version": {
        "number": 3,
        "message": "page edited v3"
    }
}
 

3. After this second update, the draft is lost and cannot be recovered.

Expected Results

The page is updated to the new version (e.g., version 3), and any draft content should remain intact until explicitly published or discarded.

Actual Results

The draft content is lost after the second PUT request, even though the status remains "current" and the version number is incremented correctly. This results in potential data loss for users relying on draft content for their page edits. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available