A space to discuss GraphQL queries, mutations, troubleshooting, throttling, and best practices.
When requesting orders using the GraphQL API we are getting duplicated FulfillmentOrder objects when the order has been fulfilled and unfulfilled in the admin interface. The FulfillmentOrders are identical other than the unique "id".
Is this intended behaviour, or is it the same fault as is described in this thread? https://community.shopify.com/c/Shopify-APIs-SDKs/Duplicate-Fulfillment-Bug-shopify-com-issue/td-p/6...
To duplicate the fault run the query
query {
orders(first: 3, reverse: true) {
edges {
node {
id
fulfillmentOrders(first: 3) {
edges {
node {
id
lineItems(first: 3) {
edges {
node {
lineItem {
name
}
id
}
}
}
}
}
}
}
}
}
}
then unfulfill and re-fulfill one of the orders, and re-run the query. You will see that there is a new fulfullmentorder.
Any help resolving this is appreciated 🙂
This is hilarious. Not in a good way, but still. I can't wait to see this in action myself.
Yea, not sure if I'm missing something or if its just working strangely.
Anyone have any thoughts on this?
So a naive process would take one of the assigned fulfillment orders, fulfill it, and then close it. So a question is, if you close one of the fulfillment orders assigned by Shopify, does the duplicated one also get closed? Since they are tied to an order, it would be interesting to know if a close assigned, is per unique ID, or per assignment.