---
title: Added parseWarnings to ShopifyqlQueryResponse - Shopify developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/posts/added-parsewarnings-to-shopifyqlqueryresponse
  md: >-
    https://shopify.dev/changelog/posts/added-parsewarnings-to-shopifyqlqueryresponse.md
metadata:
  effectiveApiVersion: 2026-10
  affectedApi:
    - displayName: Admin GraphQL API
      handle: admin-graphql
    - displayName: ShopifyQL
      handle: shopifyql
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: New
    handle: new
  indicatesActionRequired: false
  createdAt: '2026-07-15T17:25:32-04:00'
  postedAt: '2026-10-01T12:00:00-04:00'
  updatedAt: '2026-07-15T21:38:58-04:00'
  effectiveAt: '2026-10-01T12:00:00-04:00'
---

October 1, 2026

# Added parseWarnings to ShopifyqlQueryResponse

DateOctober 1, 2026

Version[2026-10](https://shopify.dev/changelog?api_version=2026-10)

FlagsNew

SurfacesAPI

Affected APIs[Admin GraphQL API](https://shopify.dev/changelog?api_type=admin-graphql)[ShopifyQL](https://shopify.dev/changelog?api_type=shopifyql)

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`:

```<gql>
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](https://shopify.dev/docs/api/admin-graphql/2026-10/queries/shopifyqlQuery)
* [ShopifyqlQueryResponse object](https://shopify.dev/docs/api/admin-graphql/2026-10/objects/ShopifyqlQueryResponse)
* [ShopifyQL query language](https://shopify.dev/docs/api/shopifyql)
* [API versioning](https://shopify.dev/docs/api/usage/versioning)