[GRAPH QL][POST][FULFILLMENT] Error has an unfulfillable status

Retired Boards Appdev Graphql Basics And Troubleshooting
1

Hello

My app is focused on creating shipping labels and updating shopify orders with the information.

We migrated to graph ql because of the same reason.

Every now and then we get an error when we create a fulfillment order

“Fulfillment order {{ORDER ID}} has an unfulfillable status= closed.”

But when we go an make a get call to see if the order was fulfilled the fulfillment is there.

We have noticed that it’s because of the fulfillmentOrderId even when the items are all in one location sometimes we get one with one item and the other one with the all of the items in the order.

How can we fix this?

2

Hey @Tendencys

Thanks for raising this! To clarify, are you stating that the fulfillment is closed before you get a chance to create the fulfillment, right?

Would you mind sharing the x-request-id when you make this call and the exact call you are making when you receive the unfulfillable status= closed and we can take a look into it. Thanks!

3

I’m having the same issue or at least very similar. Here is what I’m sending:

mutation ($fulfillment: FulfillmentV2Input!) {
  fulfillmentCreateV2(fulfillment: $fulfillment) {
    userErrors {
      field
      message
    }
    fulfillment {
      id
    }
  }
}

and here are the variables:

{"fulfillment":{
  "lineItemsByFulfillmentOrder":{
    "fulfillmentOrderId":"gid://shopify/FulfillmentOrder/4325385633978"}
}
}

Here is what i get back:

{
  "data": {
    "fulfillmentCreateV2": {
      "userErrors": [
        {
          "field": [
            "fulfillment"
          ],
          "message": "Fulfillment order 4325385633978 has an unfulfillable status= closed."
        }
      ],
      "fulfillment": null
    }
  },
  "extensions": {
    "cost": {
      "requestedQueryCost": 10,
      "actualQueryCost": 10,
      "throttleStatus": {
        "maximumAvailable": 1000,
        "currentlyAvailable": 990,
        "restoreRate": 50
      }
    }
  }
}

any help is appreciated.

4

Hey @jameslobsenz

If you’re still blocked with this, by chance did you have the request-id from when you called this mutation? It does seem like from the response that particular fulfillment order ID has been completed and closed. Let me know and I can take a look into it - thanks!

5

This still happens if you have fulfilled the order through API and then manually Unfulfilled through Admin UI. It only happens with GraphQL, not with REST.

2 Likes
6

error:Fulfillment order X99396614153X has an unfulfillable status= closed

1 Like
7

I am getting the same error after an order is edited. Is there any update on this issue?

8

Figured out my issue. I was assuming that there was 1 fulfillment per order, but this is not true. There can be multiple fulfillments per order, and when an order is edited a new fulfillment is created.