Following this guide to implement the fulfillment service, when the fulfillment order gets accepted by our fulfillment service, then the merchant try to request for cancellation. The documented way to make the REST API call is failing for both Accept or Reject calls.
Requesting a cancel in the UI doesnât work either.
Request ID: 98acfc74-8a02-4690-9744-7c8445a42775
{âdataâ:{âfulfillmentOrderSubmitCancellationRequestâ:{âfulfillmentOrderâ:null,âuserErrorsâ:[{âfieldâ:null,âmessageâ:âFailed to submit cancel request.â,â__typenameâ:âUserErrorâ}],â__typenameâ:âFulfillmentOrderSubmitCancellationRequestPayloadâ}},âextensionsâ:{âcostâ:{ârequestedQueryCostâ:11,âactualQueryCostâ:10,âthrottleStatusâ:{âmaximumAvailableâ:5000.0,âcurrentlyAvailableâ:4990,ârestoreRateâ:250.0}}}}
So, for both of these fulfillment orders involved in those request id(s), at the time the call is made (whether via the Admin or via the Fulfillment Services API client) the state of them in the database is âin progressâ, so neither of them are actually not in a state of âopenâ. Both of the fulfilment orders request status is cancellation_requested presently.
I checked backstage and this scenario isnât something that is affecting the platform at scale - I wasnât able to locate any other open issues where the errors you are facing are present. Not to say itâs a non issue though.
One question - Is this happening for any new Fulfillment orders with that specific Fulfillment Service since the last try? I saw the Fulfillment Service has the rights scopes for the calls that are being made.
If still receiving the issue, Iâd say itâs a good idea to raise this in our API bug reporting queue, as on the forums we are restricted into how much we can investigate, which in turn limits what we can pass back to partners in the Community Forums, especially if we require explicit authenticated permission to access to an app or store specifically.
While our inability to authenticate here on the forums isnât ideal, we can work around this with those x-request-Idâs youâve provided. Once authenticated, you can access the beta reporting form at - https://help.shopify.com/en/questions/partners#/contact - it sidesteps the above limitation of the forums. Feel free to reference this post if you raise a bug report. Thanks!
@Luke_K I am also seeing this same behavior using the GraphQL Admin API. My fulfillment order requests are being accepted by my fulfillment service, and the requestStatus and status fields are updated to âACCEPTEDâ and âIN_PROGRESS.â When I submit the cancellation request through the admin UI, the requestStatus is successfully updated to âCANCELLATION_REQUESTED.â However, when my fulfillment service tries to accept the cancellation request, I get the following response from the GraphQL endpoint in the userErrors field:
{ field: null, message: âCannot accept cancellation request for the fulfillment order.â }
Another issue I am seeing that may be related occurs when I make a GraphQL query to get my shopâs assignedFulfillmentOrders with an assignmentStatus of âCANCELLATION_REQUESTED.â It is not returning any fulfillment orders even though the fulfillment order mentioned above has the requestStatus âCANCELLATION_REQUESTED.â This forces me to query the fulfillmentOrders property on the shop object instead.
Exact same problem here whil developing our fulfillment service.
Cancellation Request notification comes into the system, but when I follow that up with an assignedFulfillmentOrders query for âCANCELLATION_REQUESTEDâ status it comes up empty.
This is copy - pasted exactly what the documentation says to do with no alterations.