A space to discuss GraphQL queries, mutations, troubleshooting, throttling, and best practices.
Hi,
we discovered a super strange behaviour that occurs since a few hours now.
TLDR; When fulfillments are canceled (confirmed via GraphQL API) it may occur that line items are lost.
It seems that the cancelation of fulfillments (we do it via GraphQL) does loose items if you have more than one within a fulfillment that you cancel.
In the images you see that after the last cancelation 1 of the 3 products (Mate - small is somehow lost)
This is the mutation we use to cancel the orders:
mutation fulfillmentCancel($id: ID!) {
fulfillmentCancel(id: $id) {
fulfillment {
id
}
userErrors {
field
message
}
}
}
We have automated tests that have bin running for at least 9 months now without any issue.
Since a few hours those tests throw errors since items are lost.
Hey @GerwinB,
Thanks for taking the time to share details about the behavior you noticed on orders involving unexpected totals and/or what appeared to be missing line_items on the order page. I was able to find several other reports that outlined similiar behaviors in the same timeframe mentioned in your post that our developers were already investigating.
A fix has now been implemented so you should no longer be seeing this behaviour, however it's geenrally a good idea to clear your browser cache and cookies before logging back into a shop to confirm!
- Cheers!
awwdam | API Support @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog