12 Oct 2026 Release

This note covers what shipped after the 9 Oct 2026 Release, through 12 Oct 2026. Maker-facing fixes are listed first. Recalculate work runs on the servers and needs no setting change.

Available to makers

Builder saves survive a dropped connection

If the builder loses the connection while saving, or the server answers too late, the builder checks whether that save actually landed before it asks you to save again.

A save that succeeded is kept, including new screens created in that save.
A save that did not succeed can be tried again.
A second save that arrives while the first is still finishing does not overwrite it.
Autosave waits while a publish is in progress.

Connected screens no longer freeze on an update loop

Screens that stay connected to the same app data could refresh themselves over and over until React stopped the page with a maximum-update-depth error. That loop is cut off. The screen keeps the latest data and stops dispatching the same update again.

Automation opens with its fields ready

Opening Automation no longer holds the page on a loading panel while workflow context arrives. The pane, including Get an approval fields, is there as soon as Automation opens.

Changed on the backend

Recalculate keeps order when the queue is full

Calculated properties and rollups still run on the backend. Since 9 Oct, two behaviors are tighter:

A parent keeps the place it took when it first joined the waiting line. A later edit updates the signal. It does not send that parent to the back of the line.
When the waiting line is full, each pass still works a small steady batch, so the queue keeps moving instead of stalling.

Finished recalculate signals are cleared faster

Each pass was spending several seconds deleting finished child signals in one large request. Those deletes now go out in small batches. The same pass has more time left for rollups and formulas.

A brake when the waiting line gets too long

Recalculate watches the waiting line before it changes speed.

For the first 30 minutes after the brake turns on, it only watches. The usual pace stays.
Under a comfortable line, it keeps the normal pace, and new work can still come in a little under the queue cap.
When the line is near the cap, it stays in catch-up until the line drops back down. Each pass works a smaller batch, and new work stops at a lower door so the line cannot fill all the way up.
If health checks go red, the batch gets smaller still.
While the brake is active, one sheet cannot take more than half of a pass.

There is nothing to turn on in the builder. NotionApps operations can see the brake state. Turning it off restores the previous pace.

A brief mismatch in the queue count, or a tick that runs long, no longer makes recalculate treat itself as overloaded and pause.

What makers need to do

Nothing, for existing apps.
If a builder save flickers after a slow connection, wait. A save that landed is kept.
Recalculate, the queue brake, and the Automation open fix need no migration and no new setting.