Occasional INTERNAL_SERVER_ERRORs with Next Gen Events

Loving the next gen events! We just started testing them for seeing when products are added/removed from a collection and every once in a while we’ll receive a payload like this:

[
    {
        "message": "Internal error. Looks like something went wrong on our end.",
        "extensions": {
            "code": "INTERNAL_SERVER_ERROR"
        }
    }
]

Here’s the headers for one of those requests:

Shopify-Action: update
Shopify-Api-Version: unstable
Shopify-Event-Id: 019fc803-a4d9-79fd-ab57-987d09a3250e
Shopify-Handle: collection_products_webhook
Shopify-Resource-Id: gid://shopify/Collection/XXXXXXXXXX
Shopify-Shop-Domain: xxxxxxxxx.myshopify.com
Shopify-Topic: Collection
Shopify-Triggered-At: 2026-08-03T14:25:09.849242Z
Shopify-Webhook-Id: e06aa990-c1e3-30d7-9207-c1b8545ce734

Here’s what our event toml looks like:

[[events.subscription]]
handle = "collection_products_webhook"
topic = "Collection"
actions = ["update"]

uri = "https://www.example.com/event/my-app"

triggers = ["collection.products"]

query = """
query collectionProductsEvent($collectionId: ID!, $productsId: ID!) {
  collection(id: $collectionId) {
    id
    description
    descriptionHtml
    handle
    legacyResourceId
    ruleSet {
      appliedDisjunctively
      rules {
        column
        condition
        conditionObject {
          __typename
        }
        relation
      }
    }
    sortOrder
    templateSuffix
    title
    updatedAt
    hasProduct(id: $productsId)
  }
}
"""

I realize the error might be upstream of the events and only happens occasionally in brief bursts. We do have the collection ID in the headers so we can reconcile the data that way, but it can be more expensive to figure out the collection membership change if there’s a lot of products in the collection.

Still very excited about the collection updates, their super helpful, thanks!

Hey Daniel!

Investigating this - heads up, could be bit of a wait^

Hey Daniel!

Closing the loop here - this was an error on our end and we’re deploying a fix for it. If you still see these errors after today, please feel free to let me know!

Amazing, thanks! I’ll let you know if any other pop up