Inconsistent Results When Fetching Issue Tasklists via GraphQL API

[alexis-mateo]

Select Topic Area

Bug

Body

Bug Report: Inconsistent Results When Fetching Tasklists via GraphQL API

Description

When attempting to retrieve the tasklist of a GitHub issue containing a large number of items, the GraphQL API intermittently returns an empty array for trackedIssues. This issue occurs approximately every other request, making the behavior inconsistent and unreliable.

GraphQL Query Used

{
    repository(name: "<repo_name>", owner: "<org_name>") {
        issue(number: <issue_number>) {
            trackedIssues(first: 100, after: null) {
                nodes {
                    number
                }
                pageInfo {
                    endCursor
                    hasNextPage
                }
            }
        }
    }
}

Steps to Reproduce

1. Use the above GraphQL query to fetch trackedIssues for an issue with a large tasklist.
2. Execute the same query multiple times consecutively.
3. Observe that approximately every second request returns an empty nodes array, despite the issue having many tracked issues.

Impact

This bug affects the reliability of applications that depend on accurate tasklist data from GitHub issues. It introduces uncertainty in automated workflows and data synchronization processes.

Additional Information

• This issue has been observed regardless of authentication tokens or query environment.
• No specific error messages are returned; the response is valid but missing data.

Please let me know if any additional information or logs are needed to investigate this issue further.

[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. ⭐