notion-update-page update_content batches are now all-or-nothing; calls that used to partly succeed now fail
Took effect · MCP tool notion-update-page, update_content command
Reviewed against the vendor source on Sep 24, 2026 (AI-assisted review). Key facts are re-checked against the source daily.
What changes
Previously, if one old_str in a batch matched nothing, the matching replacements were saved and the call returned success. That could silently drop content moved within a batch. Now the whole batch applies or none of it does. Empty old_str values, which were silently skipped, now fail validation, including on the REST Update page markdown endpoint.
Breaking: Calls fail after this date.
What to do
Handle a failed batch by re-fetching the page and rebuilding the edits; never send empty old_str; add a test where one replacement misses.
Strings to search for
notion-update-pageupdate_content
Counts only in files that mention notion-update-page or mcp.notion.com or notion-mcp or notion_mcp or mcp_notion or mcp__notion or notion + old_str or notion + updatemarkdown or notion + update_markdown or notion + /markdown.