Issue Summary

On some existing Confluence Cloud pages, the page emoji cannot be permanently removed.
Clicking Remove Emoji may temporarily hide the emoji. After the page properties are fetched again, the page is refreshed, or the editor is reopened, the emoji reappears.
Other content on the affected page can still be edited normally.

Steps to Reproduce

1. Open an affected Confluence page that has a page emoji.
2. Enter the page editor.
3. Open the page emoji menu.
4. Select Remove Emoji.
5. Refresh the page or reopen the editor.

Expected Results

The emoji is removed from both the draft and published page states.
The emoji remains absent after refreshing the page or reopening the editor.
Property deletion should succeed when the property exists in one storage representation but is already absent from another.

Actual Results

The emoji is not permanently removed.
The UI may initially hide the emoji, but a subsequent property read returns the unchanged emoji property and the emoji reappears.
The GraphQL request returns HTTP 200, but the mutation payload reports a failure similar to:

{  "data": {    "confluence": {      "deletePageProperty": {        "success": false,        "errors": [          {            "message": "Could not find property with key [emoji-title-draft] on page with id [<pageId>]"          }        ]      }    }  }}

The observed behavior is consistent with a content-property storage mismatch during dual-write migration:

1. The emoji property is present in the newer content-property storage.
2. The delete operation first attempts to find the corresponding property in legacy custom-content storage.
3. The legacy property is missing.
4. The operation returns early instead of continuing to remove the value from the newer storage.
5. The mutation reports success: false, while the emoji property remains readable.
6. The frontend restores the emoji during the next read.
   Both of the following properties can be affected:

• emoji-title-draft* emoji-title-published

Workaround

There is no known end-user workaround.
Customers experiencing this issue should contact Atlassian Support and reference this bug.