Notion sync issues
Work through the most common reasons a Notion sync stops behaving the way it did when you first connected.
When a Notion mirror stops updating, the cause is almost always one of five things on the Notion side rather than a problem inside Wysestats. Work the list in order.
1. The Notion connection expired
Notion access tokens can expire or be revoked from Notion's side — usually after a workspace permission change, a security event, or someone disconnecting the Wysestats integration in Notion's settings.
Fix: open Account → Connections, find Notion in the list, and click Reconnect. Complete Notion's authorization flow fully and re-share the same pages you shared the first time.
2. The page was deselected during reconnection
Notion's connection flow shows you a list of pages and asks which ones to share with Wysestats. If you skipped a page during reconnection that you originally shared, that page is now invisible to Wysestats even though the rest of the connection works.
Fix: start the reconnect flow again and explicitly tick the page that holds your planner database (or whichever resource you mirror). Re-sharing the parent page is enough — Wysestats inherits access to children.
3. The page or database was deleted in Notion
If you or a teammate deleted the Notion page that holds the mirrored database, the sync has no destination. You will see errors that look like a connection problem but are really a missing target.
Fix:
- if the page is in the Notion trash, restore it
- if the page is gone for good, recreate it, then update the planner-database mapping in Wysestats so the mirror points at the new page
4. The planner database mapping changed
Each planner database in Wysestats can be mirrored to a specific Notion page. If you renamed, moved, or replaced that mapping inside the planner settings, syncs that ran before the change can look broken even though everything is healthy now.
Fix: open the planner database in Wysestats, click into its settings, and confirm the Notion mirror field points at the page you actually want as the destination. Save. The next sync writes to the correct page.
5. You expected something other than planner sync
Notion sync rolled out in stages. Planner-to-Notion mirroring is fully live. Other Notion-side flows — for example mirroring lead submissions or archiving reports — are still rolling out and may be partial or unavailable depending on your plan.
Fix: if a non-planner Notion flow is not behaving, check the feature in Connect Notion for current scope before assuming it is broken.
Still stuck?
Capture the planner database name, the Notion page URL it should mirror to, and the time of the last expected sync. Send those to support — that combination is enough to pinpoint most cases.