14 Sep 2026 Release

Sync and Reload now say when a refresh was only partial, published forms show whether a save is still sending to Notion, and Settings → Data shows Sync Health for the whole app.

What’s new at a glance

Capability	What you can do	Learn more
Database health	See Up to date, Partial, Held, Waiting, or Access blocked after Sync / Reload	Reload and sync
Honest reload toasts	A partial or paused refresh no longer looks like a full success	Reload and sync
Published form save state	After submit, users see Saved in NotionApps, Sending to Notion, Confirmed in Notion, or Needs attention	Form submit redirection
Sync Health	Open Settings → Data for app and database status, recent runs, Sync Now / Retry, and a prefilled support ticket	Settings → Data

Reload does not remove rows unless we finished reading the database.
A save is kept if Notion is rate-limiting or the job restarts.
Double-submit does not create a second Notion page.

Features

1. Database health after Sync / Reload

The builder now tells you whether we finished reading Notion:

Health	Meaning
Up to date · Compared …	We finished reading. Extra local rows that Notion deleted can be removed.
Partial · more rows than we could read	We did not finish. Extra local rows were kept.
Held · cleanup paused. Nothing was removed	A large cleanup was paused on purpose.
Waiting · changes are sending to Notion	App edits are still going out.
Access blocked · reconnect Notion	The integration cannot read the workspace. Reconnect, then refresh.

Reload will not remove rows unless we finished reading the database. If we only got part of a large database, Sync says so. It does not silently drop rows.

2. Reload toasts

Toast	When you see it
Refresh was partial. Extra local rows were kept.	The read did not finish.
Refresh was partial. This database has more rows than we were allowed to read. Nothing was removed.	The database is larger than the read window.
Reload finished, but a large cleanup was paused. Nothing was removed.	Cleanup was held.
Refreshed recent changes. Nothing was removed.	Optimized resume of recent edits.
Notion is asking us to wait. Your save is kept and will retry.	Notion rate-limited the connection.
Notion access is blocked. Reconnect, then refresh.	Token or sharing is broken.

3. Published form save state

After a published Create or Update form succeeds locally, the popup keeps your custom success title. The detail line is the save state:

State	Meaning
Saved in NotionApps	We accepted the row. Notion does not have a page yet.
Sending to Notion	The write is in flight or retrying.
Confirmed in Notion	The Notion page exists.
Needs attention	The create was lost mid-flight. We will not open a second page. Contact support if it stays here.

A save is kept if Notion is rate-limiting or the job restarts. Submitting the same form again does not create a second Notion page.

4. Sync Health (Settings → Data)

Open Settings → Data for the app-level view:

overall status, last successful sync, active syncs, and issues
one row per connected database with Sync Now, Retry, View details, and Create ticket
current issues and recent sync history

Sync Now and Retry run the same builder Sync / Reload as Databases. Retry asks for confirmation. Pause / Resume stays with NotionApps support. End users never see this pane.

What makers need to change

Goal	Extra work
Read health and toasts	None — Publish / refresh as usual
Use Sync Health	None — open Settings → Data
Keep a custom form success message	None — it stays the title
Teach end users the new save-state line	Optional — point them at the four states above