My Latest Change Doesn't Appear In the Live Site

Have you just recently made a change in Confluence which doesn’t seem to appear in your live site?

Symptom

Your site’s update strategy is set to live updates. One or more changes you made in the Confluence content that is published to a Scroll site or changes you made in your site’s settings don’t seem to be automatically reflected in your live site.

Explanation

There are some known limitations to live updates. Some types of changes are known to not trigger a live update, at least not on their own. These types of changes are:

Changing a space name, key, logo or description.
Changing a Scroll document summary or cover cover image.
Converting pages from the Confluence legacy to the new editor, individually or in bulk.
Setting up a new or editing an existing context key in a Scroll document.
Moving a root level page.
Changing a page attachment in Confluence (update or delete) without editing the Confluence page.

These types of changes will only reflect in your live site if you’ve combined them with other changes that do trigger a live update.

Resolution

In order to be able to troubleshoot this problem, please try the following steps, in the same order as detailed below.

Check the site update status

First, you should check if the site update was actually triggered but not completed yet. To do this:

From the My Sites screen, click the card that has your site’s name.
From the left sidebar, click Site updates.

The Site update screen will open. You will see a table where each row represents a change that was made or is going to be made to your live site. Check if there might still be an update in progress. In that case, wait for the update to be completed and then check your live site again.

Manually trigger a full site update

If the Site update screen doesn’t indicate an update that is still in progress or if it already completed but your change is still not in your live site, then it’s fair to assume that your change has not been able to trigger an update at all.

Please proceed to manually trigger a full site update as described on Manually Trigger a Full Site Update .