Hi there,
for a couple of days, bulk operations on a concrete store are suddenly constantly failing. Please could you take a look?
Some recent request IDs:
3f03a336-51a9-4691-a4fa-1863138f2682-1762181683
536e0638-4dce-4103-9b24-9560a3dbb0e9-1762181674
3060f27d-f726-44d2-9045-884e2e19eaf0-1762181546
463f222b-6ace-4fd6-92d1-64b2c6620912-1762181365
ea6f7811-d7f2-4b64-ac21-d022729af712-1762181350
Hey @sinuhe, can you share a little more context on the operations that have started failing?
From FAQ - Shopify Developer Community Forums :
Hi,
it fails when checking status:
query {
currentBulkOperation {
id
status
errorCode
url
partialDataUrl
createdAt
completedAt
objectCount
rootObjectCount
}
}
And also when creating a new bulk operation:
mutation {
bulkOperationRunQuery(
groupObjects: false, query: ""\"
{
products (query: "published_status:published") {
edges {
node {
id
handle
productType
title
description
vendor
publishedAt
updatedAt
tags
featuredMedia {
preview {
image {
url
altText
}
}
}
variants {
edges {
node {
id
title
availableForSale
barcode
price
compareAtPrice
sku
image {
url
altText
}
}
}
}
collections(query: "collection_type:custom") {
edges {
node {
id
title
}
}
}
}
}
}
}
""\"
) {
bulkOperation {
id
status
errorCode
url
partialDataUrl
createdAt
completedAt
}
userErrors {
field
message
}
}
}
The API version is 2025-10, the error is:
Internal error. Looks like something went wrong on our end.
Request ID: 401a0e58-ea68-48ab-a54c-8c69c1845dd1-1762249815 (include this in support requests).
Hi @sinuhe, can you share the bulk operation ID? The request ID’s I see here look to be associated with the query for the status, not the job itself.
Can you also test to see if this is working by paginating through as a non-bulk query? The reason for this is to narrow down the cause. If the error occurs in a non bulk operation, then there’s likely an issue with the data on the affected store. That will require reaching out to help.shopify.com so we can look in to the specific store details.
On the other hand, if it’s only failing with bulk queries, there may be something specific with the bulk operations itself causing the failure.
Let me know what you find.
Hi there,
finally, I saw that the problem was in the query currentBulkOperation ( currentBulkOperation - GraphQL Admin ), and I also saw this recent post in the changelog: New Queries for Bulk Operations - Shopify developer changelog
I could find a workaround to skip these failures on our side… but the failures started more or less after the publication of the post. It says “If You’re Using Existing Bulk Operation Workflows. No changes are necessary. The currentBulkOperation can still be used but is being deprecated.“, but it is not apparently completely true.
Could you take a look at that? Thanks and kind regards.
Great find. Thanks for sharing that. It looks like there have been other reports of this here too: currentBulkOperation query failing on one shop
I’ll dig in to both of these and see what I can find out.
Hi, ok, thanks.
Related to this, I was trying the new bulkOperations query (bulkOperations - GraphQL Admin), with the API version 2026-01:
query {
bulkOperations(
first: 1
sortKey: CREATED_AT
reverse: true
) {
nodes {
id
status
errorCode
url
partialDataUrl
createdAt
completedAt
objectCount
rootObjectCount
}
}
}
But it always returns a Shopify internal error:
Internal error. Looks like something went wrong on our end.
Request ID: b678ed57-53c5-41ac-9c30-aa82bd3ecad1-1762416701 (include this in support requests).
However, with GraphiQL it works… please could you take a look?
A fix has been deployed and the internal server error should be resolved.
Hi there, the error with the the new bulkOperations query ( bulkOperations - GraphQL Admin ), with the API version 2026-01, is failing again. It was working on the weekend but today it is suddenly failing.
Could you take a look?
query {
bulkOperations(
first: 1
sortKey: CREATED_AT
reverse: true
) {
nodes {
id
status
errorCode
url
partialDataUrl
createdAt
completedAt
objectCount
rootObjectCount
}
}
}
Hey @sinuhe, I’m unable to replicate this on my end. Can you share the response you received and the request id from the failure? If you query by the exact ID, does it return the operation you are looking in to?
Hi there,
I just tested it and it is working again, did you make any changes? I can see that this query is considerably slower than currentBulkOperation, but that’s not a big problem for us.
I’ll be testing it for a few days and will let you know if it fails again.
Thanks.
Thanks for sharing it’s working again. If you do see failures let us know.
Regarding performance, if you add the specific ID to your query, is it returned faster?
Hi there,
it is failing again. Some requests IDs:
d642c9fc-84b7-4c8f-b93e-d69c6069e87a-1763648747
bf781e40-1dbe-439c-932b-ae07b2eb3a6c-1763648743
cf4d757e-1522-48a1-90fe-a2096abb4f54-1763648737
59392af8-6ebe-4606-8409-cf3afcde9481-1763648731
7c65a7ef-7ec1-41fe-8bbe-bc2bdcc2774c-1763648727
Thanks for sharing that @sinuhe. From what I can see these are timing out. Is this happening consistently now, or was it limited to a specific time range?
Hi @KyleG-Shopify ,
Consistently. Here are some requests IDs happened a few minutes ago:
29a6aaed-96d9-4173-bfb4-a2564e221f23-1763714862
c39d0faa-948b-4092-8718-dc75ec7d80d4-1763714869
d305820c-c3d9-42db-934f-4713b63227e6-1763714853
371d36c3-d007-46ee-bac1-dd971c264d71-1763714864
69c4c288-97af-4320-8b25-276230a2ff4f-1763714870
Hey @sinuhe, thanks for the updates. After digging in to this, I can confirm this is an issue we’re aware and actively working on it. These new queries will be much more reliable and performant when 2026-01 becomes stable in the new year.
Appreciate your patience and detailed reporting on this.