Internal error on notifications graphQL query

Hi Shopify - I’m getting an Internal error:
Shopify GraphQL API returned an error: [{“message”:“Internal error. Looks like something went wrong on our end.\nRequest ID: 95d48478-085f-42ff-89aa-231e0a797610-1743754963 (include this in support requests).”,“extensions”:{“requestId”:“95d48478-085f-42ff-89aa-231e0a797610-1743754963”,“code”:“INTERNAL_SERVER_ERROR”}}]

graphQL version is 2024-07

The related query is:

query ($numItems: Int!, $cursor: String, $locale: String!){
  translatableResources(first: $numItems, after: $cursor resourceType: EMAIL_TEMPLATE) {
    pageInfo {
      hasNextPage
    }
    edges {
      cursor
      node {
        resourceId
        translatableContent {
          digest
          key
          value
        }
        translations(locale: $locale) {
          key
          value
        }
      }
    }
  }
}

I’m getting an error for this query on multiple stores (at least 6). The issue seems to have been around for 2 days or so.

Notably, the error only crops on on specific translation languages. I have been able to reproduce this on German, French and English where default translations are provided by Shopify, but not on Arabic and Icelandic where no translations are present

Would it be possible to check this? Looking forward to hearing from you! :slight_smile:

2 Likes

We’re also seeing a recent uptick in the number of 5xx errors coming back from Shopify. In our case it’s mostly with the inventorySetQuantities mutation, but we’re also seeing it with other GraphQL queries and mutations (as well as some REST calls). Same situation as OP - currently using 2024-07, seeing this happen with multiple stores.

Hey @Vera_Auflauf :waving_hand: - thanks for sharing the request ID there - I was able to pull the error in our logs. I think I was able to replicate this internally.

I’ll reach out to our developers for you and loop back with you folks here when I have next steps to share - thanks for reporting this!

Hi @Alan_G,

thank you so much for looking into this!
Do you happen to know if there is any update on this? We are getting more and more reports from our merchants on this issue.

1 Like

It looks like it’s working again :smiley:
thank you!

1 Like