Filters misbehave for the returns endpoint

We have noticed that when we use a warehouse_id to filter results from the “returns” endpoint, the “first” field that we use to limit the results is filtering before the warehouse_id filter.
We therefore obtain a number of results lower than expected. (using first:5 may return 3 results while first:10 may return 7).
Would you please fix that ? Thank you.

 {
    returns(
      customer_account_id: $customerAccountId
      date_to: $dateTo
      date_from: $dateFrom
      warehouse_id: $warehouseId
    ) {
      data(
        first: $first
      ) {
        pageInfo {
          hasNextPage
          endCursor
          hasPreviousPage
          startCursor
        }
        edges {
          node {
            id
            order_id
            created_at
            total_items_expected
            total_items_received
            total_items_restocked
            order {
              partner_order_id
              order_number
            }
          }
        }
    }

Hi @PierreM
Thanks for the heads up!
Is there any chance you could share those two request IDs?
Thanks in advance!
Tom

Hi @tomasw
Thank you for your support.
We have made two requests for the example:

  • 60116dc11868b15b4c807392 with a “first” set to 10 and we obtain 7 results
  • 60116e0707a3aad27cc85603 with a “first” set to 20 and we obtain 16 results

Hi @PierreM!
I apologize for my delayed update about this.
We have already submitted a ticket for our engineers to work on this.
The results are correct (there are no results omitted), but the amount of results returned is less than expected.
Thanks for catching this!
We will let you know as soon as we have an update about it.
Tom

Hello @tomasw , do you have any visibility regarding this anomaly ? Thank you

Hi @PierreM!
We don’t have an update yet, but we will raise the priority of this to see if it can be addressed soon.
We will keep you updated on the progress.
Thanks again for the patience!
Tom