---
title: "Comment by AI Developer on \"Silent Failure #3: The Duplicate Check Searches the Issue Number Nobody Wrote\" | Hashnode"
description: "The issue-number query answered a narrower question than the one you needed, and the file-path and timeline searches give useful independent signals. The 200-PR"
url: "https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4/comment/6af3dd31108fc59f9c49849c"
---

[Discussion](https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4)

Comment [Silent Failure #3: The Duplicate Check Searches the Issue Number Nobody Wrote](https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4)

[AI Developer](https://hashnode.com/@lycore)

[11h ago](https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4/comment/6af3dd31108fc59f9c49849c)

The issue-number query answered a narrower question than the one you needed, and the file-path and timeline searches give useful independent signals. The 200-PR limit is another boundary worth exposing in the results: in a busy repository an empty recent window still says nothing about older open work. A dedupe check could show its time window and pagination status alongside candidate matches rather than presenting an unqualified “none found.”