Page syncing occurs when site visits or dashboard refreshes trigger publishing updates, and inconsistencies can be resolved by performing two force refreshes on each page to trigger background refresh and update content in the browser.
How does page syncing between Notion and Super work?
Page publishing updates are triggered by site visits or the dashboard refresh button, and one or two visits to the page will see any inconsistencies ironed out as the updated content and CSS is rolled out across the pages.
When you are developing a site, your content can be cached before updating
When you are developing a site, a page can be built by Super with a certain set of content and CSS code. This built page is published and cached to our Content Delivery Network, and if you're also browsing the site, it can also be cached by your browser.
Use force refresh to pull the latest content
If you see inconsistencies, please perform two force refreshes on each page 5-10 seconds apart - one to trigger the background refresh of the page by Super and one to get the updated content to the browser. Refreshing more often than 5 seconds will not make the content sync faster as we have to wait for the cache to expire.
There are different keyboard shortcuts for force refreshing a web page depending on the browser and operating system being used. The link provided does not contain a comprehensive list of these shortcuts. However, a common shortcut is to press
Ctrl + Shift + R on Windows or
Command + Shift + R on Mac. This will bypass the cached version of the page and reload the most recent version from the server.