Error on collections with 2025-04 version

New GraphQL Product APIs
,
1

We are experiencing failures (INTERNAL_SERVER_ERROR) when making a specific call to the 2025-04 API version. The call can be found below.

We have narrowed it down to the “column” attribute on the collections/ruleSet/rules object. If we remove the “column” attribute from the query, the error stops. This only happens on certain accounts (can provide details as necessary) and does not happen at all on 2025-01.

This is keeping us from migrating to 2025-04, which will cause us issues with new installs using the new markets features. Please help!

{
  collections(first:200) {
  pageInfo {
    hasNextPage
  }
  edges {
    cursor
    node {
    legacyResourceId
    description
    handle
    title
    updatedAt
    productsCount {
      count
    }
    ruleSet {
      appliedDisjunctively
      rules {
      condition
      column
      conditionObject {
        ... on CollectionRuleMetafieldCondition {
        metafieldDefinition {
          id
        }
        }
        ... on CollectionRuleProductCategoryCondition {
        value {
          id
        }
        }
        ... on CollectionRuleTextCondition {
        value
        }
      }
      relation
      }
    }
    sortOrder
    image {
      altText
      height
      width
      originalSrc
    }
    products(first: 100) {
      pageInfo {
      hasNextPage
      }
      edges {
      cursor
      node {
        id
        title
      }
      }
    }
    }
  }
  }
}
2

Hey @Sam - I did a little testing within my test environment and wasn’t able to replicate the error on my end.

Could you share the shop IDs where you’re seeing the issue pop up. If you’re able to as well, could you share an X-Request-ID value from the response headers we send out? I can take those and dig a bit further into our logs.

Happy to help with this though!

3

Hi Alan,

Thanks for getting back to me. Some Shop IDs below:

  • 68948459740
  • 53525479596
  • 78437810498
  • 9227468897

A sample x-request-id for shop id 68948459740 would be 84e9403b-0b3f-4a7b-b36b-cc6d4e0d5194-1743520447

Just note that it happens every time we make the call for any of the shops above.

Thanks,
Sam

4

Hi @Alan_G - any updates on this?

5

Hey @Sam :waving_hand: - thanks for sharing that request ID. I was able to pull the error in our logs on my end here. It does look like something odd is happening on our end. I’m still not able to replicate the issue internally, but I’ll touch base with our devs now that we’ve narrowed down the error in the logs and I’ll loop back with you once I have more info - hopefully speak with you soon!

8

Hey again @Sam - I’ve escalated this up to our developers who are looking into this as a potential issue on our end. I can’t guarantee an exact turnaround time on a possible fix, but I’ll keep you in the loop here :slight_smile:

9

Hi Alan,

Really appreciate your help on this. As you can imagine this is critical for us, as it is keeping us from moving to the latest production version of the API. This is important not only because we like to be on the latest version, but because of the email below from Shopify.

- The new Markets will begin rolling out to stores in April, only to merchants using compatible apps. Stores using your app(s) will be eligible to use the new Markets once your app(s) have been updated to API version 2025.04 or later.
- Merchants using the new version of Markets will receive a warning that the app is not compatible at the time of install.

So this has become quite urgent for us.

Thanks,
Sam

10

Hey @Sam - no worries at all, happy to help and thanks for waiting on this. Just wanted to loop back with you here - we have a fix that should be deployed shortly - could you let me know if you still see the issue after 24 hours or so (it can take a bit of time for fixes to propagate).

If you’re still seeing this pop up by this time tomorrow, just ping me here and we can take a look. Hope this helps :slight_smile:

11

Looks to be fixed. Thanks @Alan_G!!!

1 Like