🐛 fix: recover when duplication lands on parent#189
Merged
Conversation
…le> 1' with retries
🐳 Docker Build Completed!Version: Pull ImageDownload the Docker image to your local machine: docker pull evalsysorg/mcpmark:pr-fix-notion-state-manager-59a0db1Run EvalExecute evaluation tasks using the built image: DOCKER_IMAGE_VERSION=pr-fix-notion-state-manager-59a0db1 ./run-task.sh --models gpt-4.1-mini --tasks file_context/uppercaseImportant This build is for testing and validation purposes. |
xyliugo
approved these changes
Sep 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Type
Description of Change
Fix Notion duplicate navigation by searching newest "<title> (1)" when URL is invalid
When Notion duplicates a page, the UI can occasionally navigate to the parent page instead of the new duplicate. This change adds a recovery path that:
Waits briefly (5s), then searches for the exact title "<title> (1)" in the source workspace.
Retries the search (3 attempts, 5s gaps) to account for eventual consistency.
Chooses the newest match and navigates to it, then continues the standard move/rename logic.
This makes duplication robust against occasional misnavigation without altering the existing flow.
Additional Information