App reviews, troubleshooting, and recommendations
Hi all, Do you notice a change with the bulk operation (GrahpQL API)? The upload to Google Cloud Storage work well until 2 days and now it return me a 400 error with this message :
<?xml version='1.0' encoding='UTF-8'?><Error><Code>InvalidArgument<\/Code><Message>Invalid argument.<\/Message><Details>Cannot parse success status code: private<\/Details><\/Error>
The file content did'nt have change.I'm stuck on this. Help will be appreciate. Thx
Go to the solution
This is an accepted solution.
I figured out what my problem is.
I was setting the parameters of the call manually from the stagedUploadsCreate mutation call.
But like it nows write in the docs it's no more with AWS but with Google Cloud Storage.
The response of stagedUploadsCreate have change and it's not the same key parameters and not the same order that before.
The simple way to passed params to the pushing call is to put the params like the stagedUploadsCreate returns.
In my case I just change the key "value" to "contents" to feat with my HTTP Client.
An another error was related to this change in the bulkOperationRunMutation.
Before that I was taking manually in the return of stagedUploadsCreate for getting the stagedUploadPath URL.
Of course as the return has changed it causes an error.
I now take the url from the param who have the name "key".
For summary, my error was to write manually the params in my HTTP call and not put it like the stagedUploadsCreate mutation return.
View solution in original post
Explore the 30-30-30 rule, a dynamic social media strategy for new businesses. Learn how t...
Discover how to leverage the often overlooked footer of your ecommerce site to gain custom...
In this blog, we’ll be shining a light on Shopify Partners, Experts, and Affiliates. Who a...