Recent 400 Errors Referencing CloudFlare

GraphQL Admin API Troubleshooting
,
1

Hi,

Similar to another issue I posted related to 5xx errors from Shopify, we’re also seeing an uptick recently in 400 errors coming back from Shopify for GraphQL queries and mutations we know are valid.

Using the same example as that other post (the inventorySetQuantities mutation) we’re seeing many instances where we will send an inventory update for an inventory item successfully, then a bit later we will send that same mutation for that same inventory item (albeit with a different quantity) and receive a 400 response, then a bit later we will once again send that mutation for that inventory item and get a 200 response. Each time we get a 400 responce code we also get a response body that mentions Cloudflare (pasted below) so I’m guessing the issue lies somewhere between Shopify and Cloudflare.

Like the 5xx errors, this is another “mental blocker” in terms of fully migrating to the GraphQL APIs because it doesn’t give the team a lot of confidence moving forward. Thankfully we have retry logic built into our use of the APIs, but if the 400 errors persist longer than our retry logic then it poses problems for us. Is there any investigation or work being done to improve the reliability of these APIs prior to the deadline for forced migration?

400 response body

<html>

<head>
    <title>400 Bad Request</title>
</head>

<body>
    <center>
        <h1>400 Bad Request</h1>
    </center>
    <hr>
    <center>cloudflare</center>
</body>

</html>
2

Hey @ktbishop :waving_hand: - we can take a look into this for you for sure - would you happen to have X-Request-ID values from the response headers for both the 5xx (from the other thread)/4xx errors you’re seeing? I can use those to grab the example errors here directly in our logs.

If not, no worries, I can do a bit of digging using the shop/app IDs as well as a timestamp if you can share one (down to the second would be great if possible!)

Hope to hear from you soon.

1 Like
3

Hi @Alan_G,

I’m also talking to @KyleG-Shopify over in the other thread, just letting you know so we aren’t all stepping on each others toes.

I do have x-request-id values for the recent 503s and 400s. Just let me know if you want them posted here or if you’d prefer DMs.

I mentioned this to KyleG as well, but we’re also seeing some 502s mixed in. Those don’t have IDs for me to share, unfortunately, but those response bodies reference CloudFlare as well:

<html>
<head>
    <title>502 Bad Gateway</title>
</head>
<body>
    <center>
        <h1>502 Bad Gateway</h1>
    </center>
    <hr>
    <center>cloudflare</center>
</body>
</html>
1 Like