Notion update_content batch fails with validation_error because one old_str is empty or matches nothing

Symptom

validation_error naming an old_str that wasn't foundupdate_content call that used to partly succeed now leaves the page unchangedvalidation_error on an empty old_str

Cause

Since 2026-08-25, notion-update-page applies every content-changing replacement in a batch or none. One missing old_str now fails the whole call, and an empty old_str, once silently skipped, fails validation on both the MCP tool and the REST markdown update. On 2026-10-16 this changed again: partial matches are applied and misses are listed in warnings, and the request fails only if no content-changing edit matches.

Fix

Send only non-empty old_str values that exist on the page. Read the warnings array (codes no_match or indentation_mismatch) after each update, and re-fetch the page if a miss is reported.

ApplyCopy

Check response.warnings after every update_content call; treat any no_match entry as a failed edit and re-fetch the page before retrying.

Affected

Notion MCP and Update page markdown, behavior changed 2026-08-25 and again 2026-10-16

Sources

• https://developers.notion.com/page/changelog

Last verified 2026-10-24 · Confirmed by 0 builders