We are rejecting fulfillment requests when there are issues with the orders that need to be fixed. However some of them will automatically fix themselves so we query every hour to get the rejected fulfillment orders and try to import them. The way we are doing it now is using graphql assignedFulfillmentOrders but it does not allow you to send an assignmentStatus of rejected or add a query to the request. Therefore we have to query for all open orders and then filter for the ones that are rejected. This can take a long time if we have a lot of open orders. Is there a way to query for just the rejected fulfillment orders?
Topic summary
A developer is seeking a more efficient way to query for rejected fulfillment orders in GraphQL.
Currently, they reject fulfillment requests when orders have issues, some of which resolve automatically. Their hourly process queries all open orders using assignedFulfillmentOrders and then filters for rejected ones, which becomes slow with high order volumes.
The core issue: The GraphQL endpoint doesn’t support filtering by assignmentStatus of “rejected” or adding query parameters to narrow results upfront.
Status: The question remains unanswered—no alternative API methods or workarounds have been suggested yet.