articles GraphQL query is returning empty response having hasNextPage set to true

Retired Boards Appdev Custom Storefronts

Topic summary

Storefront API articles query returns an empty result while pagination flags suggest more data: HTTP 200 with empty articles (edges/nodes), pageInfo.hasNextPage = true, and endCursor = null. These are GraphQL pagination fields indicating whether more pages exist and the cursor to fetch them.

Context: Admin REST API by blog ID works, but business need is to fetch all articles via GraphQL. The issue appears isolated to at least one store; other stores behave correctly.

Shopify response: Could not reproduce on test stores (with and without articles). Advised contacting Partner Support (App Development and API) for direct investigation.

Additional report: Another developer sees the same symptoms, linked in their case to a deleted customer account with the same email as an active account. With first: 1, edges/nodes are empty, hasNextPage remains true, endCursor is null—suggesting a pagination inconsistency potentially tied to account data.

Status: Unresolved. Action items: open a Partner Support ticket for the affected store; consider checking for duplicated/deleted customer accounts with the same email as a possible contributing factor.

Summarized with AI on February 1. AI used: gpt-5.
1

We’re using articles GraphQL Query to fetch articles of the store. Attached is the cURL request and response payload. The API responds with 200 status code with empty articles array as well as true in hasNextPage field and null endCursor

Although the Rest API to fetch articles by blog is working as expected.

But our business need is to fetch articles by graphQL as it provides to fetch all articles instead of fetching by blog id.

We’re having the same functionality in multiple stores and it seems to be working fine.

2

Hi alokwizzy,

Thanks for your post. When testing on a couple test stores where one had blog articles and one did not the issue described with pageInfo values didn’t occur. So if you’re able to consistently have it happen on that one store please [request email assistance from Partner Support] using the ‘App Development and API’ topic to enable a more direct investigation.

3

This is happening for us too. In our case it is because of a deleted customer account with the same email as an active account. If you include “first:1” in the query, the edges and nodes are empty arrays, hasNextPage is true, but endCursor is null.