Forcing a page to update: HubPeople Help

What it does

Your pages are served as ready-made HTML for speed. When you edit a page, the platform rebuilds that ready-made version for you. Force page Update simply triggers that rebuild on demand for one page, so the live page is regenerated from your latest content.

When to use it

Use it when a change you made to a page is not showing on the live page after a short wait. Because rebuilds normally happen automatically, this is just a manual nudge for the rare occasion one is delayed. It is a per-page action: you run it on the specific page that looks out of date.

How to force a page to update

Open your brand and go to the Pages tab.
Find the page in the list, click its three-dots (⋮) menu, and choose Force page Update.
A short message explains that it will rebuild the page. Click Force Update.
Allow a few moments, then refresh the live page. If it still does not show after waiting, contact support.

A page's three-dots menu with Force page Update highlighted; the page's last rendered time and version are shown just beneath it. — The page's three-dots menu, with Force page Update highlighted.

The Force Page Update confirmation dialog, which names the page and explains that the action rebuilds the page on the front end, that changes normally update automatically, and to allow a few moments after refreshing. — The confirmation explains exactly what will happen.

Checking the Page Render Status

To be sure a page has finished rebuilding, open it in the editor (the Edit option) and look for the Page Render Status indicator near the top. It updates on its own every few seconds, so you can watch a rebuild complete.

The Page Render Status indicator showing a green tick, Up To Date with a version number (v37) in brackets, and a Last Rendered At time of 4 days ago. — The Page Render Status indicator, showing the version and when the page last rendered.

It shows one of four states:

Up to date: the live page matches your latest content. Nothing to do.
Pending: a rebuild is queued and about to start.
Rendering: a rebuild is in progress.
Failed: the last rebuild did not complete. Use the refresh button next to the status to try again, and if it keeps failing, contact support.

Next to the status you will also see two extra details: a version number in brackets, like Up to date (v12), which ticks up each time the page is rebuilt, and a Last Rendered At time showing how long ago the page last finished rendering, like 2 minutes ago. Together they let you confirm that a rebuild has actually happened, and when.

After a Force page Update, the status moves through Pending and Rendering, then settles on Up to date once the page has been rebuilt, with the version stepping up and the last rendered time resetting to a moment ago.

Force page Update vs Clean Stale HTML

These two are easy to mix up, but they do different jobs:

Force page Update (page level, in the three-dots menu) rebuilds one page so your latest edits appear. This is the one to use when a page looks out of date.
Clean Stale HTML (brand level, in About your brand) removes leftover pages you have deleted or moved. It does not refresh or regenerate the content of your existing pages.

So if a page is not showing your changes, use Force page Update, not Clean Stale HTML. See Cleaning up stale pages →

Good to know: you should rarely need this. Pages rebuild on their own when you make changes; Force page Update is here for the occasional time an update is slow to appear.