Known Limitations

These are customer-relevant boundaries of Better Pages Release 13.2 for Confluence Cloud, not a list of every Confluence limitation. For a failed workflow, use Troubleshooting and Support.

Migration and platform

Better Pages does not automatically read or convert another vendor’s private Data Center app data or macros. Plan a manual content review for a Data Center migration rather than expecting the Cloud app to transform those pages. The Release 13 existing-installation upgrade check concerns this Better Pages Cloud app, not third-party Data Center conversion. See the Overview and FAQ.

Composer and published content

Reopen a Home-created page after publishing

Direct Composer Publish on a new private draft is fixed and verified on production. After publishing, the original Home Continue designing result can still retain draft context and report that Confluence cannot read the page. Open the published page and select its Smart Designer byline instead; this loads the current published version. Do not create another page or repeat Publish to resolve a stale Home result. See Composer.

Other content boundaries

• Composer can preview the current Confluence editor draft from its in-editor launcher, but cannot apply a page-level change over that unsaved editor work. Save or close the editor, then open Composer from the published page’s Better Pages byline for a reviewed write. See Composer.
• Composer’s native-block editing covers supported headings, paragraphs, lists, quotes, code, panels, dividers, and simple tables. Existing macros, complex tables, and media are protected rather than silently rewritten. Edit those in their appropriate Confluence or macro editor. See Composer.
• A published Brand Style is a snapshot. Editing or unpublishing its preset does not restyle pages already saved with it. Reapply the current published choice when updating a page. See Brand Kits and Brand Styles.

Page and space operations

Previously affected Tabs groups

Release 13.1 fixes newly authored structured groups losing their separate tabs after save/publish/reopen. It does not automatically reconstruct groups already contaminated by the earlier bug, such as an old group collapsed into Overview.

Release 13.2 separately fixes older Composer resource cards not loading inside Tabs at render time, without changing saved page content. This rendering repair is not a migration of previously damaged tab structure. Preserve affected content and contact support before attempting a structural repair; do not delete sections or repeatedly resave the group. See Tabs.

Other operation boundaries

• A Delivery journey creates published linked pages after confirmation; it is not the private single-page draft used by other page templates. Check the space and hierarchy before creating it. See Templates and Better Pages Home.
• Space Manager operations run with your Confluence permissions and may stop after some items succeed if permission or page state changes. Review the completed-operation list and refresh before retrying; do not rerun a full selection blindly. See Space Manager and Troubleshooting.
• In the current Tabs group editor, deleting a tab also deletes its owned rich-content section. Review that section before confirming the edit. See Tabs.

If one of these boundaries changes, the linked feature guide is the detailed procedure; this page is a quick evaluation checklist.