Issue Summary

Users experience an intermittent issue where newly created or published Confluence pages and blog posts return a "Couldn't find this page" / "Page Not Found" error immediately after publishing. The content becomes accessible after a 1-3 minute delay or a manual browser refresh. Repeated clicks on Create during this window produce duplicate drafts. Root cause is a read-after-write consistency failure introduced when publish mutations moved from REST to GraphQL without equivalent read-replica consistency handling.

Environment

• Product: Confluence Cloud
• Affected Site:cOne speciifc customer 

Browser: Chrome 145 on Windows 10 (from HAR analysis)

Steps to Reproduce

1. Open a Confluence space (shared or private).
2. Click Create → Blog post, the space "+" blog button, or Create (standard page).
3. Add content in the editor and click Publish.
4. Observe: Redirected to the target URL but UI shows "Couldn't find this page" / deleted-page state instead of the published content.
5. Wait 1-3 minutes or perform a single browser refresh — content appears at the same URL.

Occurrence Pattern: Intermittent; predominantly mornings (06:00-08:00 UTC); improves later in the day. First observed 2026-02-03, recurred on multiple dates through late February.

Expected Results

After clicking Publish, the user should be immediately redirected to the newly published page or blog post, with the content fully rendered and accessible.

Actual Results

• Redirect lands on the correct URL but UI shows a "Couldn't find this page" or "page not found" error screen.
• Backend confirms content is written to the database with content_status = current — the publish write succeeds.
• Subsequent GraphQL reads return 404/403; collab token returns 403 with reason RESOURCE_DELETED; editor aborts to the not-found screen.
• After 1-3 minutes or a manual refresh, the page loads normally at the same URL.
• Blog posts created via the "+" button may produce multiple "Untitled DRAFT" entries if users click repeatedly.

Root Cause: Read Replica Lag / Read-After-Write Consistency Failure

Workaround

• After clicking Publish, wait a few seconds before taking additional actions.

• If a not-found error appears, perform a single browser refresh — content should load.

• Avoid repeated clicks on Create/Publish to prevent duplicate drafts; delete extra drafts if they appear.