Packs_per_day query not reporting correct data for the date filter

Hi,

We want to run a query every 15 minutes to check on the recent packs and ensure items were all scanned.
But looking at the response of packs_per_day with date_from and date_to filter, it is returning results 5 hours and 51 minutes ahead.

Below is the query with the date range filter.

query {
    packs_per_day(date_from: "2021-05-26T14:30:03" date_to: "2021-05-26T14:30:04") {
            request_id
            complexity
            data {
            pageInfo {
            hasNextPage
            hasPreviousPage
            startCursor
            endCursor
        }
        edges {
            node {
                    id
                    shipment_id
                    warehouse_id
                    total_items
                    unique_items
                    barcodes_scanned
                    user_first_name
                    user_last_name
                    created_at
                    order {
                        id
                        order_number
                    }
                }
            cursor
            }
        }
    }
}

This query returned result with created_at: “2021-05-26T20:21:03”.

request_id: “60f008f1bba32db49eb08add”

Hi,
I just did the same query,

query {
  packs_per_day(
    date_from: "2021-07-16T12:00:03"
    date_to: "2021-07-16T14:00:00"
  ) {
    request_id
    complexity
    data {
      pageInfo {
        hasNextPage
        hasPreviousPage
        startCursor
        endCursor
      }
      edges {
        node {
          id
          shipment_id
          warehouse_id
          total_items
          unique_items
          barcodes_scanned
          user_first_name
          user_last_name
          created_at
          order {
            id
            order_number
          }
        }
        cursor
      }
    }
  }
}

and the results included “order_number”: “002183194” which seems to be spot-on for the results. I am not too sure why May is giving you problems, and it would be very difficult to go back that far. Do you have a recent example of the same issue?

Hi Theresa,

Below is the recent example with request_id,
which is also returning results 5 hours and 51 minutes ahead.

query {
  packs_per_day(
    date_from: "2021-07-16T12:00:00"
    date_to: "2021-07-16T12:01:00"
  ) {
    request_id
    complexity
    data {
      pageInfo {
        hasNextPage
        hasPreviousPage
        startCursor
        endCursor
      }
      edges {
        node {
          id
          shipment_id
          warehouse_id
          total_items
          unique_items
          barcodes_scanned
          user_first_name
          user_last_name
          created_at
          order {
            id
            order_number
          }
        }
        cursor
      }
    }
  }
}

This query returned result with created_at: “2021-07-16T17:51:48”
request_id: “60f28e6e3268dd09e92befb1”

For Packs and Picks per day API:

the inconsistency of user details in the response of Shiphero API, there are some user’s data that will be available in the API response, but the same user information itself is not present on the Shiphero platform screen. The same happens vice versa, user packer logs are not present in API response while it’s available on the screen.

for example,

  • if you check the logs from API response for April 6th and July 8th: Tekita Williams, this user is not available on the ShipHero screen but API fetched picker logs for him/her.
  • 27-5-2021 12:38 pm CST in screen, Nate Reynolds packer log not available in Shiphero API response.

the above is only what we have caught, but there may exist more such inconsistencies.

Please have a look at it.

I will send the 5 hour difference that packs_per_day is returning over to engineering. Thank you for the very direct example!

Hi Theresa,

Any update on this?

It is still in the queue. I will see if I can get it prioritized. Thank you for the heads up!