When you reference a Notion database item inside another page, the mention does not always update automatically when the source page is edited. This can cause confusion when you rely on that mention to show current information. The cause is that Notion caches the mention preview until the page containing the mention is refreshed. This article explains how to force a database mention to reflect the latest edits on the source page without manually rebuilding the mention.
Key Takeaways: Refresh Database Mentions After Page Edits
- Ctrl + F or Cmd + F then Escape: Forces the page to reload the mention preview from the database.
- Page navigation away and back: Closing the tab or sidebar and reopening the page triggers a full cache refresh.
- Relation and rollup formulas: These update automatically only when the source property changes, not when the source page title or body is edited.
How Notion Database Mentions Work and Why They Lag
A Notion database mention is an inline reference to a specific database item, such as a row in a table or a page in a gallery view. You create it by typing @ followed by the page name. The mention displays a small preview card with the title, a property snippet, and a link to the source page.
When you edit the source page — for example, you change its title or update a property — the mention preview does not always update immediately. This happens because Notion stores a snapshot of the mention data in the page cache. The cache refreshes only when the page loads from scratch. If you keep the page open in a tab or the sidebar, the cached preview stays unchanged.
This behavior is different from a database formula or a rollup, which recomputes when a related property changes. A mention is a static link with a cached preview, not a live computed field. Understanding this distinction helps you choose the right tool for each situation.
Steps to Force a Database Mention to Show the Latest Source Page Data
- Refresh the page with the mention
Press Ctrl + R (Windows) or Cmd + R (Mac). This reloads the entire Notion page and forces the mention cache to update. If you are in the desktop app, use the same keyboard shortcut or close and reopen the app. - Use the find shortcut to trigger a re-render
Press Ctrl + F (Windows) or Cmd + F (Mac) to open the find bar, then press Escape to close it. This action forces Notion to re-render the visible part of the page, including mention previews. It works faster than a full page refresh. - Navigate away and return
Click a different page in the sidebar, then click back to the original page. This loads the page from the server again, clearing the cached mention preview. For sidebar mentions, close the sidebar panel and reopen it. - Toggle the database view
If the mention is inside a linked database view, switch the view to a different layout (for example, from Table to Board) and then switch back. This refreshes the data source for all mentions in that view. - Use a rollup property instead of a mention
If you need the mention to update automatically when the source property changes, create a rollup in the target database. A rollup pulls data from a related database and updates whenever the source property is modified. This is not a direct replacement for an inline mention, but it is the only way to get live updates without manual refresh.
If the Mention Still Shows Old Data After Refresh
Mention in a public page or share link
Public pages and share links cache mention previews aggressively. Even after refreshing your own view, visitors may see stale data. Ask visitors to reload the page by pressing F5 or Cmd + R. For critical data, avoid using mentions on public pages. Use a synced database block instead.
Mention shows the wrong page after renaming
If you rename a page that is mentioned elsewhere, the mention still links to the correct page but the preview may display the old name. Delete the mention and recreate it by typing @ followed by the new name. This ensures the cached preview matches the current title.
Mention in a template button or recurring template
Template buttons create a copy of the mention at the moment the template is applied. Edits to the source page after the template is applied do not affect the mention in the newly created page. To update such mentions, you must delete the mention and reinsert it manually. Consider using a database relation with a rollup instead of a mention inside templates.
Mention in a comment or discussion thread
Comments that contain a database mention do not update the preview when the source page is edited. The comment is a snapshot of the mention at the time it was posted. There is no way to force a comment mention to update. If you need to share updated information, post a new comment with the current mention.
Database Mention vs Rollup vs Relation: When to Use Each
| Item | Database Mention | Rollup | Relation |
|---|---|---|---|
| Description | Inline link with cached preview | Live computed value from a related database | Connection between two database items |
| Updates automatically | No, requires manual page refresh | Yes, when the source property changes | No, but the relation link is always live |
| Best for | Short references in meeting notes or docs | Aggregating numbers or text from related items | Building relational data models |
| Limitation | Stale preview until refresh | Cannot display inline inside a sentence | Requires a dedicated property column |
Use a database mention when you need a quick reference that looks natural in a sentence. Use a rollup when you need live data from a related item. Use a relation when you need to link items and create bidirectional lookups.
After applying the refresh methods described above, your database mention should show the most recent edits from the source page. For ongoing projects, consider replacing mentions with rollups or linked database views if stale data becomes a frequent problem. A useful advanced tip: create a button in the target database that triggers a page reload via the Notion API to automatically refresh all mentions in that workspace.