[BUG] Shopify GraphQL API is flip-flopping between Fulfillment Order Supported Actions

Products and Orders APIs
1

There seems to be a bug in the Shopify GraphQL API at the moment.

Running a query to get ‘fulfillmentOrders’ from an Order through the official Shopify GraphiQL App App results in: Internal error. Looks like something went wrong on our end.\nRequest ID: db063678-15ba-4d95-8456-b5aaa6f991f4-1744105658 (include this in support requests).

Doing the same query via my PHP client, does yield a response, but the supportedActions data is either:

"supportedActions" => [
                  [
                    "action" => "HOLD",
                  ],
                ],

Or:

"supportedActions" => [
                  [
                    "action" => "CREATE_FULFILLMENT",
                  ],
                  [
                    "action" => "HOLD",
                  ],
                ],

It literally changes between requests, and there is NO change happening in the background to affect stock levels.

It’s important to note too that the updatedAt timestamp does NOT change between each time it either says both actions, or one.

1 Like
2

Have just confirmed that this is affecting the REST API as well.

3

Hey @roberttolton :waving_hand: , thanks for reporting this. I was able to pull some logs here and I think this may be an issue on our end. Would you be able to share an X-Request-ID from the REST API example error you saw’s response headers as well if possible?

I just want to narrow down the issue to see if it’s the same thing happening both in REST/GraphQL. My next step will be to dig a bit deeper into this, but just wanted to touch base to see if you could share that REST request ID if possible too.

Hope to hear from you soon!

5

Hi Alan,

Sure, here is the REST API Request ID from it having only the ‘hold’ action incorrectly: 710191d5-c605-4199-9834-7f04fa8cead9-1744114960

6

Thanks Robert, appreciate you sending that my way. I took a closer look at our logs, and it looks like this might have been happening for you on multiple orders, so this is pretty odd. I’ll keep digging into this and loop back with you when I have more info on our end.

8

Hey @roberttolton :waving_hand: - just following up with an update here. It looks like this might be an issue on our end and we’re continuing to investigate, but I have a workaround that may work in the meantime.

Looking at the logs, it looks like the instance of the GraphiQL app you were using didn’t have the read/write_fulfillments access scopes enabled.

If you’re able to, could you head to this link here: Shopify GraphiQL App — Install and add the read/write_fulfillments access scopes to the app (along with any others you previously used/need)? If you click the install link after inputting your myshopify.com URL there, it should trigger a pop-up asking if you’d like to approve the additional scopes rather than uninstalling/re-installing the app. The shop owner may need to do this part if you don’t have staff access to manage app installations.

For your other app though, it does seem like it had the necessary read_fulfillments scopes enabled, so if adding the scope to the GraphiQL app doesn’t resolve the issue on that end, just let me know (as well if you still see any issues on the GraphiQL side of things.) and I’ll add that to our investigation notes here.

9

Hi @Alan_G I added the scopes to the GraphiQL App which solved the Internal Server Error, however the fulfillmentOrders edges are always empty.

Even if I copy a working query from my PHP app, to the GraphiQL app and run it, the data is empty. Even though I know that query works because the data is sitting in my PHP app’s database.

10

Thanks for trying that @roberttolton - would you be able to share the full GraphQL query you’re making where you’re seeing the empty edges array?

I’ll see if I can replicate what you’re seeing internally on my end here and loop back with you on this :slight_smile:

12

HI @Alan_G sorry for the late reply. Here’s the query:

query GetOrder($id: ID!) {
  order(id: $id) {
    id
    fulfillmentOrders(first: 250) {
      edges {
        node {
          supportedActions {
            action
          }
          fulfillmentHolds {
            reason
            reasonNotes
          }
          updatedAt
        }
      }
    }
  }
}

{
  "id": "gid://shopify/Order/5790690934938"
}
13

Hi @roberttolton - thanks for sharing that and no worries. We’ve been doing some digging into this and we think it may actually be a potential issue on our end that’s causing the error. I’ll keep my eyes on this for you and loop back with you here when I have some more info to share - let me know if I can help with anything else in the meantime though