Internal error. Looks like something went wrong on our end. Request ID: 7cae4d4f-30b5-43ab-b37e-1cc

Hey!

I’m doing a bulk mutation call to update product images alt text and it fails randomly. The bulk mutation is updating the alt text for product images. It works 99% of the time - but seeing new errors today. Errors happened twice over 1000’s of successful updates.

<<-'GRAPHQL'
mutation($stagedUploadPath: String!) {
bulkOperationRunMutation(
mutation: "mutation call($media: [UpdateMediaInput!]!, $productId: ID!) { productUpdateMedia(media: $media, productId: $productId) { media { alt } userErrors { message field } } }",
stagedUploadPath: $stagedUploadPath) {
bulkOperation {
id
url
status
}
userErrors {
message
field
}
}
}
GRAPHQL

I’m getting the following message after attempting the post:

"Internal error. Looks like something went wrong on our end.\nRequest ID: 7cae4d4f-30b5-43ab-b37e-1ccddc5d600b (include this in support requests)."
Internal error. Looks like something went wrong on our end.\nRequest ID: e054bc5b-f902-4ec4-96eb-4c711024ebba (include this in support requests).

Please help me solve this issue :slightly_smiling_face:

Thanks

Arjun

Hey @arjun_rajkumar ,

I was able to take a closer look at the info and example x-request-id values you shared for the internal errors.

Our documentation for Bulk Operations covers expected failures such as internal errors, as well as suggestions for handling operation failures here. Whether your app polls for status or uses the bulk_operation webhook. The partialDataUrl field can also be helpful in the case that part of the data was created, returning a partially completed data file to help build a new request.

Hope this offers you a starting point - Cheers!