Incident: closed pull requests are not showed in list page

[ti-chi-bot]

🏷️ Discussion Type

Bug

Body

Incident: closed pull requests are not showed in list page, such as pingcap/tidb repo

Hi, I am an ORG owner of pingcap, now we investigating the issue affecting the pingcap, tikv, and pingcap-inc organizations.

I tried the gh cli and the web page, but it both have the issue.

I reproduced the issue: close a pull request and then watch it in the pull request closed list. I can see it after closed it at soon, but it disappeared when I list the page again after 10 minutes

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[wuhuizuo]

I also encountered this problem.

[froddd]

We also have this problem, and to confirm this also applies to merged PRs:

• Empty list of closed PRs: https://github.com/ministryofjustice/hmpps-single-accommodation-service-ui/pulls?q=is%3Apr+is%3Aclosed
• Link to PR that should appear in list: SAS-264: Add Next actions card ministryofjustice/hmpps-single-accommodation-service-ui#162

[lydiaralphgov]

Us too: https://github.com/hmcts/pre-api/pulls?q=is%3Apr+is%3Aclosed

[froddd]

Further to previous comment, we have since merged another PR which does appear in the closed list: https://github.com/ministryofjustice/hmpps-single-accommodation-service-ui/pulls?q=is%3Apr+is%3Aclosed

However, we're still missing all previously PRs😟

[scazan]

same here

[parlato-vooma]

We also have this problem - seems like it applies to both open and closed PRs.

[teto-ri]

Same issue on our private org repository.

[EricTendian]

Also experiencing this problem, it seems to be a search index issue as any page that uses search for filtering PRs does not show the full list. As a workaround, using the API or CLI (gh pr list) goes to the source of truth and provides an accurate list - just don't use the --search arg.

[obryckim]

We're seeing the same thing on multiple repositories.
The closed PR list is either zero or just 1-2 items (even when we have 100+ closed PRs).
Getting the list of closed PRs from the API is returning the true list.
Also, navigating to those PRs directly (e.g. https://github.com/org/repo/pull/123) works fine too.

UI shows 2

API shows all 97

[froddd]

Our occurrence of this issue was resolved shortly after submitting a support ticket. Presumably some level of caching isn't working quite right, which wouldn't be that surprising given the reliability hiccups the whole service has been suffering from recently.

[marcin-sg]

This worked for us as well - thnx for sugestion @froddd.

The solution from github support:

We have indexed the issue to address the issue.

No root cause was given.

[P-r-e-m-i-u-m]

Yo @ti-chi-bot — this is actually critical. Losing PR history in a massive repo like tidb is a nightmare scenario for audit trails.
That 10-minute disappearing act screams "backend replication lag" or a failing cache invalidation job. Since it affects both the CLI and the web, it's definitely not a frontend bug—it's deep in their data stack.
Since you're an Org Owner, I'd recommend escalating this to GitHub Support directly. Standard community reporting might be too slow for something this widespread. 🔧

[ti-chi-bot]

I escalated this to GitHub Support directly, but also too slow to get the solution and notification on githubstatus.com site.

[jmmgreg]

Also experiencing the issue, any update?

[divyeshlahane]

I checked on Friday and that seemed to be resolved but seems like the issue is back again -

[LongYC]

Seems like similar issues are reported on #193463 and #192108

[charlieforward9]

Opened a special case to this https://github.com/orgs/community/discussions/200085