I had a closer look here, and while we aren’t able to locate store or app details, there are still few insights to share based on the error. Here are a few questions I like to work through:
Where was the id initially returned from? A webhook, request, etc? Was the entire payload logged, or just pertinent fields? Have there potentially been updates to the order/fulfillment since the data was returned?
Have you confirmed that other related details are valid? Eg. Confirmation of order_id?
This error is generally returned when a resource can’t be found, and there are cases where an id may no longer be available. Additionally, there would be a similar outcome if the id isn’t a valid fulfillment_order_id (FulfillmentOrder.id). These ideas are occasionally confused with fulfillment_id (Fulfillment.id) or order_id (Order.id), all of which will be unique.
Is this happening with every fulfillment order?If not, additional troubleshooting could include confirmation that fulfillment order exists via a GET request, or similar request to the related order resource.
If this is happening with multiple fulfillment orders, please log and share examples of x-request-id response header values returned with the error - we can take a closer look for logs and pass on next steps - Cheers!