---
title: "Forge known limitations for Numbered Headings"
canonical: "https://support.appfire.com/space/NH/2536538162/Forge%20known%20limitations%20for%20Numbered%20Headings"
format: markdown
---
The Numbered Headings app has been migrated to the Forge platform for Cloud. While this transition brings improved performance and better integration with Atlassian's ecosystem, it also introduces some platform-specific limitations due to the current capabilities of the Forge framework.
This document outlines the current known limitations of the Numbered Headings app in the Forge. Each limitation includes a description of the issue, available workarounds (if any), and references to related Atlassian tickets for tracking purposes.
If you encounter any of these issues or have questions about workarounds, please refer to the ticket numbers provided or contact support for assistance.
> Macro (toc)
## 1. Page-level numbering not updating for restricted pages
Page-level numbering doesn't update pages when they are restricted. This is because restricted Confluence pages don't trigger page events (such as create, update, view, or copy) to Forge apps.
**Workaround**
Add the app system user to the restricted pages in page share to receive and process page-level numberings.
**Atlassian Tickets:** [ECO-961](https://jira.atlassian.com/browse/ECO-961?utm_source=chatgpt.com) / [CONFCLOUD-82583](https://jira.atlassian.com/browse/CONFCLOUD-82583?utm_source=chatgpt.com)
## 2. Byline dialog stays open after closing the Page-Level numbering configuration screen
When you open the *Page-Level Numbering Configuration* screen through a [content byline item](https://developer.atlassian.com/platform/forge/manifest-reference/modules/confluence-content-byline-item/). The configuration screen loads correctly, but after closing the screen—whether by saving or simply closing—the original byline dialog stays open in the background instead of closing.
**Workaround**
Click outside the byline to close the dialog.
**Atlassian Ticket:** [FRGE-1878](https://ecosystem.atlassian.net/browse/FRGE-1878)
## 3. Pages using the legacy editor do not receive page-level and macro-level numbering updates
Pages using the legacy editor are not compatible with page-level or macro-level numbering features. The Forge Confluence macro is not available on the legacy editor.
**Workaround**
Update and convert the page to the latest Cloud editor.
**Atlassian ticket**
The legacy editor is being deprecated in Confluence Cloud. For more information see:
- [Forge Confluence macro not available on legacy editor](https://community.developer.atlassian.com/t/forge-confluence-macro-not-available-on-legacy-editor/67690/9)
- [The Legacy Editor is being deprecated in Confluence Cloud: Here’s what you need to know](https://community.atlassian.com/forums/Confluence-articles/The-Legacy-Editor-is-being-deprecated-in-Confluence-Cloud-Here-s/ba-p/3046832)
## 4. Page content shifts left after editing and publishing
After a page is edited and then published, the page content unexpectedly shifts to the left instead of maintaining its normal alignment. This misalignment occurs only after publishing and not while editing. The issue affects the overall layout and readability of the page, making the content appear offset or improperly styled.
There is currently no workaround available.
**Atlassian tickets:** [ECOHELP-95280](https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-95280) / [PCS-3703489](https://support.atlassian.com/requests/PCS-3703489/)
## 5. Page-level configuration modal closes on outside click
The Page Numbering Configuration modal closes if you click outside of it, causing you to lose any unsaved settings. This makes it difficult to complete or save your changes.
There is currently no workaround available.
**Atlassian ticket:** [FRGE-1855](https://ecosystem.atlassian.net/browse/FRGE-1855)