translatableResources GraphQL returns INTERNAL_SERVER_ERROR for PRODUCT

GraphQL Admin API Troubleshooting
1

App Type

Public Shopify App (multi-tenant)

API: 2025-10

API

Admin GraphQL API

Query Causing Issue

{translatableResources(resourceType: PRODUCT,first: 250,after: “eyJsYXN0X2lkIjo4MDE3MDM2NDQzOTEyLCJsYXN0X3ZhbHVlIjoiODAxNzAzNjQ0MzkxMiJ9”) {edges {cursornode {resourceIdtranslations(locale: “cs”) {localekeyvalue}}}}}

Error Response

{
  "errors": [
    {
      "message": "Internal error. Looks like something went wrong on our end.\nRequest ID: c34ebac3-60f7-4e51-b3e8-2e5652405fdc-1772203458 (include this in support requests).",
      "extensions": {
        "requestId": "c34ebac3-60f7-4e51-b3e8-2e5652405fdc-1772203458",
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ],
  "data": null
}

{
  "errors": [
    {
      "message": "Internal error. Looks like something went wrong on our end.\nRequest ID: 4835a90a-1b3e-4ea7-8838-3ff907aaabf2-1772203198 (include this in support requests).",
      "extensions": {
        "requestId": "4835a90a-1b3e-4ea7-8838-3ff907aaabf2-1772203198",
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ],
  "data": null
}

My client’s store is currently unable to retrieve translation data because it is stuck on the above error. Can Shopify Supporter help me check the cause?

1 Like
2

Hey @localoca, it looks like those requests are timing out. Try reducing first to 50 or 100 and paginate through the results using cursor-based pagination.

If you’re worried about rate limits from making more requests, GraphQL rate limiting is based on the calculated cost of each query, not requests per second like REST. Smaller pages actually cost less per request.

For really large catalogs, bulk operations are worth looking into as well. They run asynchronously and aren’t subject to the same timeout constraints.