Fixes for the most common hiccups right after you duplicate a TrueStack system. Most take under a minute.
This is the most common duplication hiccup, and it's on Notion's end, not the system. Notion sometimes needs a moment to recalculate formulas and rollups in a freshly duplicated workspace.
Close the tab, reopen the system from your own workspace sidebar (not the original link), and give it 30–60 seconds. If a number still looks wrong, open that specific database and click into the formula/rollup property to confirm the source column is still linked correctly.
Do a hard refresh (Cmd/Ctrl+Shift+R) or fully close and reopen the page. Notion occasionally fails to finish copying an image asset during duplication, and a reload usually re-fetches it.
If it's still missing after a refresh, message us with the page name and we'll patch it in personally.
Synced blocks occasionally break their link when Notion copies a system into a different workspace. Refresh the page first.
If the block is still empty or wrong, note which page it's on and contact us — we'll re-sync it from the source for you at no charge.
Give Notion a moment to finish indexing your new copy, then hard refresh.
If you're on mobile, try opening it in a desktop browser or the desktop app first — Notion's mobile renderer is more prone to layout quirks right after a duplication than desktop is.
Make sure you're logged into Notion (or create a free account first — no paid plan required), then open the link again.
If it still fails, try an incognito/private window in case a cached session is interfering, or switch which Notion workspace is active if you belong to more than one.
Linked database views can take a minute to finish populating after duplication. Refresh the page.
If rows are still missing, check whether a filter got carried over unexpectedly — open the view's filter settings and confirm nothing is hiding your data.
Message support with your order email and the name of the page that's acting up. We'll either walk you through the fix or repair it directly. This is never a reason for a refund on its own, since it's a quick fix, not a defect in the system — see our Refund Policy for how we handle genuine defects.
Still stuck? Contact us. We reply within one business day.