Fixed
A change was made so update-page calls that would delete pages now fail and require review of the pages intended for deletion before they can proceed.
The issue
Bug: `replace_content` and `replace_content_range` trash child pages and databases
— the original title of makenotion/notion-mcp-server issue #171, quoted as written. The issue has no error text of its own.
What fixed it
We implemented a change that requires an additional flag `allow_deleting_content` when there are page deletion in update-page calls. In future operations, if an update results in a page deletion, then the tool call will fail and require a review of pages to intended for deletion.
— a maintainer's comment on the issue.
Source and dates
| Repository | makenotion/notion-mcp-server |
|---|---|
| Issue | Bug: `replace_content` and `replace_content_range` trash child pages and databases |
| Evidence | a maintainer's comment |
| Status | Fixed (per the evidence) |
| Fixed in | No version is named |
| Issue closed | 2026-03-03 |
| Read from GitHub | 2026-11-07 |
| Approved by a person | 2026-11-07 |
This page records what the vendor's own GitHub repository says. The error text, the issue title and the quote are copied as written; the summary at the top is one sentence limited to the quote, and a person approved this fact on 2026-11-07. KanseiLink has not re-run the fix. Read the issue before applying it. Something changed? Write to contact@synapse-arrows.com.
For AI agents
The same fact is returned as issue_facts by lookup({ service_id: 'notion' }) on the KanseiLink MCP server (https://mcp.kansei-link.com/mcp), next to the other checked facts for Notion. Connection guide: Notion service page.