---
title: "Page changes and changes in the publishing state"
canonical: "https://support.appfire.com/space/CPCL/646611272/Page%20changes%20and%20changes%20in%20the%20publishing%20state"
format: markdown
---
> Macro (aura-html)
## Publishing byline state and page changes
A source space page and the published page of the target space remain in sync until an action triggers an Atlassian page update event.
## User actions on a published and synced page
The following actions on a published page in either the source or target space affect the publishing state and cause a change in publishing state, for example, a [SYNCEd] page moves to a different publishing state such as[out of sync].
> 📝 A page may need to be refreshed after the change to display the updated publishing state byline.
| **User action** | **Sets publishing state as:** | **Notes** |
| --- | --- | --- |
| **Edit a page** in either source space or target space | [out of sync] | |
| **Move a page in the source space that includes a change in the hierarchy** | [out of sync] | - changes in the order for a page that do not include a change in the hierarchy (changing the page ordering) do not change the publishing state for the page
- Changes in a parent page’s macro content as the result of a page move, for example, `children` macro, do not change the publishing state for the parent page. |
| **Move a page in the target space that includes a change in the hierarchy** | [no change in status] | - next publishing action from the source space can cause the target space page to be moved |
| **Add a label** to either the source space page or the target space page | [out of sync] | |
| **Remove a label** from either the source space page or the target space page | [out of sync] | |
| **Add an attachment **to either the source space page or the target space page | [out of sync] | |
| **Delete an attachment** from either the source space page or the target space page | [out of sync] | |
| **Check or uncheck the box for any macro**, for example, in a Confluence task macro on either the source space page or the target space page | [out of sync] | > 📝 Multiple changes in a macro in a short period of time, for example, checking several tasks as completed, may only cause one Confluence update as Confluence Cloud may process these changes in a batch process. |
| **Archive published page in the source space** | - publishing sync is removed from the target space page
- publishing sync is unchanged on the target space page
- the publishing state byline is still displayed on the target space page
- no publishing state is displayed on the archived source space page | Any edits to the target space page whilst the source space page is archived sets the publishing state on the target space page as [out of sync].
> ℹ️ Restoring a page from the archive sets the publishing status as [out of sync] on each page and enables the page to be published and synced from the source space. |
| **Archive published page in the target space** | - publishing sync is unchanged on the source space page
- publishing state dialog box link to page version in each space is retained on each page
- the publishing state byline is still displayed on the source space page
- no publishing state is displayed on the archived target space page | An edit to the source space page, while the target space page is archived, causes the publishing state as [out of sync] on the source space page.
> ℹ️ Restoring a page from the archive sets the publishing state as [out of sync] on each page and enables the page to be published and synced from the source space. |
| **Delete a published and synced page from the source space** | - the target space page is appended with the [REMOVED] lozenge
 | Publishing the source space page creates a new page even if the deleted target space page has been **restored from trash**.* |
| **Delete a published and synced page from the target space** | - publishing sync on the source space page is changed to [NEW] | |
| **Restore a page from the source space trash**
> ℹ️ With a previously published target space page has not been deleted. | A ‘**restored from trash**’ source space page will be restored with the publishing state at the time of deletion (if there have been no changes to the target space page)
The publishing state dialog includes a link to the target space page | |
| **Restored page from target space trash**
> ℹ️ With a previously published source space page has not been deleted. | A **restored from trash** target space page is restored with the publishing state at the time of deletion (if there have been no changes to the source space page).
The source space page retains the [NEW] publishing state until a new publishing action. | > ℹ️ If the archived target space page has not been restored, any publishing action on the source space page creates **a new page** in the target space.*****
If a new page has been created by a publish action, restoring the deleted page in the target space trash offers two options
- overwrite newly created target space page (and maintain sync link for restored page)
- restore the deleted page with a new title (with no sync link to any page in the source space)
> ⚠️ Restoring a page from the trash might restore the page to the root of the space. |
| > 📝 ***** Publishing to a target space with an existing page that has the same page title as a source space page may cause publishing problems. You may need to rename pages or remove pages before publishing. |
> ℹ️ A user viewing a page does not cause any change in the publishing state.
> ✅ Atlassian update events related to some of these user actions do not necessarily increment the Confluence version of the source space page, but a publishing action increments the target space page Confluence version. For example, adding a label does not increment the page version in a source space, but publishing this change increments the target space version.