---
title: >-
  Events subscription query complexity limit is changing to 100 points - 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/events-subscription-query-complexity-limit-is-changing-to-100-points
  md: >-
    https://shopify.dev/changelog/events-subscription-query-complexity-limit-is-changing-to-100-points.md
metadata:
  effectiveApiVersion: ''
  affectedApi:
    - displayName: Events & webhooks
      handle: webhook
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: Breaking API Change
    handle: breaking-api-change
  indicatesActionRequired: true
  createdAt: '2026-09-22T12:09:47-04:00'
  postedAt: '2026-09-22T14:00:00-04:00'
  updatedAt: '2026-09-22T14:00:00-04:00'
  effectiveAt: '2026-09-22T14:00:00-04:00'
---

September 22, 2026

# Events subscription query complexity limit is changing to 100 points

DateSeptember 22, 2026

Flags[Breaking API Change](https://shopify.dev/changelog?filter=breaking-api-change)[Action required](https://shopify.dev/changelog?action_required=true)

SurfacesAPI

Affected APIs[Events & webhooks](https://shopify.dev/changelog?api_type=webhook)

We’re reducing the query complexity limit for Events subscriptions from 250 to 100 points. This change does not affect Classic Webhooks.

Shopify assigns each Events query a complexity score based on the fields it selects, the types of data those fields return, and the number of items requested in connections using first or last, following the [GraphQL query cost calculation](https://shopify.dev/docs/apps/build/apis/graphql-admin/rate-limits#cost-calculation). The limit applies to each subscription query, and queries executed by Events subscriptions don’t count toward your app’s [API rate limits](https://shopify.dev/docs/api/usage/limits).

### What to do

Review subscription queries that exceed 100 points and shape each subscription around the changes your app handles:

* **Split subscriptions by the work they do**: You can configure multiple subscriptions for the same topic, each with its own triggers and query.
* **Query the changed resource directly**: For example, for a variant price change, query the affected variant’s price, SKU, and parent Product ID instead of fetching the Product’s first 250 variants. This avoids repeatedly fetching unchanged variants and covers changed variants beyond the first page.
* **Match queries to available variables**: A variant price trigger provides `$variantsId`, but a product title trigger doesn’t. Use separate subscriptions when changes require different query variables.

Preserve the fields and related data your handler needs when splitting queries. See the [guide to optimizing your subscriptions](https://shopify.dev/docs/apps/build/events/optimizing-your-subscriptions) for examples and data coverage checks. If your use case needs more than 100 points, let us know in the [community forums](https://community.shopify.dev/t/events-query-complexity-limit-is-changing-to-100-points/37888).