Added parseWarnings to ShopifyqlQueryResponse

Starting in API version 2026-10, the shopifyqlQuery query in the GraphQL Admin API returns a new parseWarnings field on ShopifyqlQueryResponse. This field surfaces non-fatal issues, such as the use of fields scheduled for deprecation, so you can detect and address them proactively.

What changed

shopifyqlQuery now returns a parseWarnings field alongside your results. The field is always present: it returns a list of warning messages when a successful query has non-fatal issues, and an empty list when there are none.

Unlike parseErrors, which explain why a query failed to run, parseWarnings are only returned on queries that ran successfully, together with tableData. Warnings don’t block execution, but they highlight potential problems you should consider fixing.

Why this matters

Warnings help you identify and resolve issues before they cause failures, such as upcoming deprecations or other changes that could affect your queries in future API versions. By monitoring parseWarnings, you can keep your ShopifyQL queries compatible as the API evolves.

What to do

Add parseWarnings to your shopifyqlQuery selection set, and check it after a successful query in the same way you already check parseErrors:

query {
  shopifyqlQuery(query: "FROM sales SHOW total_sales SINCE -7d") {
    tableData { columns { name } rows }
    parseWarnings
    parseErrors
  }
}

In this example, parseWarnings will contain any non-fatal warnings related to the query, or an empty list if there are none.

Learn more

• shopifyqlQuery query reference
• ShopifyqlQueryResponse object
• ShopifyQL query language
• API versioning