Notion offline cache: missing staleness bound for concurrent edits

Notion offline cache staleness bound

The goal is to define the maximum age or condition under which a locally cached Notion page is considered stale and should be refreshed after a concurrent edit occurs on the server.

Currently, Notion does not publish an explicit staleness threshold, and observed refresh behavior varies between the web application, desktop clients, and mobile apps, leaving users without a clear constraint on when cached content updates automatically.

What is the defined staleness limit for cached pages? Does this limit differ across Notion’s web, desktop, and mobile platforms? Is there a user‑accessible way to force immediate cache invalidation or configure the refresh interval?