3 Oct 2026: Scheduling date, sync holds, and the Recalculate rollout

Announcements
1

Now live: a Scheduling date field for booking forms, sync holds that put you in charge of missing rows, and a run of login, builder, and live-demo fixes. On the backend, the Recalculate engine has been rebuilt on its own server and has started a staged rollout.

This post is split the same way as the release note. Available to makers is what you can open and use in the builder or the published app today. Changed on the backend is work that shipped on the servers; there is nothing new to click for those items, and they are listed so you know what changed under your app.

Full release note: 3 Oct 2026 Release

Available to makers

Capability What you can do
Scheduling date A new date field for forms with its own rules: Closed days, Holidays, Earliest day, Booking window, Hours, and Time zone. The calendar hides what the rules forbid, and the server checks the same rules again on save. Two fields on one form can keep different calendars.
Sync holds A short Notion read never deletes rows. A complete read that is still missing many rows (100 or more, or 10 % of a database with at least 100 rows) goes on hold. In Settings → Data → Sync Health the row shows N not in Notion and two buttons: Keep these rows or I removed these in Notion. Nothing is removed until you answer, and then only on the next complete read.
Recalculate switch The per-field Recalculate in NotionApps switch from 16 Sep now updates its status line on save and is honored end to end. A field turned off is left out entirely.
Email & password Choosing Email & password with an email column in Users setup now enables Confirm.
Tall sign-up forms A mobile-view app opened on a desktop no longer clips the password field or submit button. The card grows with the form and scrolls inside the frame when it must.
Builder fixes Add Filtering on a related list with no filter yet saves the first filter again. Mobile create links keep the reference that links the new record to its parent. Create New App no longer crashes on /home. The Manage Databases empty-list hint says what to do.
Live demo Get demo code stays visible when the first fetch of the demo list fails. Shared demo personas recover from the one-time-code limit.

How to use the new pieces:

Changed on the backend

Recalculate engine. Recalculation now runs as its own process on a dedicated host, so a long compute never delays a save or a sync. It computes rollups from the synced related rows, including rows past the first 25 Notion’s page API returns, keeps a good number once computed instead of letting a later sync overwrite it with Notion’s capped value, re-queues a parent only when one of its inputs changed, passes formulas it cannot parse through from Notion, and pauses itself on Mongo latency, work timeouts, or host load (three strikes, with Sync unaffected).

Where it stands. The engine is on in production behind a guarded canary: a fixed 5 % slice of parent rows as of 3 Oct, promoted or rolled back on the server from its own health checks. Most apps still show Notion’s page value for rollups over more than 25 linked pages, and that is expected while the slice is small. Leave Recalculate in NotionApps on for the fields you want included; when the rollout reaches your rows, Home starts serving the computed number without a republish. Nothing in the builder speeds this up. A later release note will say when the rollout has reached all apps.

Sync reliability.

  • Writes Notion rate-limited (429) were marked done and left on Sending. They now retry with a wait and turn Synced on their own.
  • Long Notion reads get up to 3 hours instead of 30 minutes, so very large databases finish.
  • The sync scheduler recovers from transient errors instead of stopping quietly.
  • Deleting a row in the app before its create or update reached Notion now cancels that write, so the database goes back to its normal schedule instead of being picked up every couple of seconds.
  • Sync holds are stored with the decision, who made it, and when; removal applies only on the next complete read.

Support and operations. Support sees the same hold you see in Live Operations and can record the same two choices, so one audited decision applies no matter who made it. Recalculate rollout health is visible to support.

What makers need to change

Goal Extra work
Booking form that refuses closed days or out-of-hours times Add a Scheduling date field. Set Closed days, Hours, and Time zone. If you add hours, set Show date/time to date and time.
Rows missing after a sync Settings → Data → Sync Health → Keep these rows or I removed these in Notion.
Rollups or hours that stop at 25 linked pages None you can take today. Leave Recalculate in NotionApps on; the backend rollout reaches your app in stages.
Writes stuck on Sending None. Rate-limited writes retry on their own.
Email & password login Pick the email column in Users setup and confirm.

Docs

How to use it

Related troubleshooting

Release notes