Picks_per_day query not reporting correct data when using "date_from" - off by 60-80 seconds

We run a query every 5 minutes to check on the recent picks and ensure items were all scanned and items all had weights, etc. This was working fine until a few months ago, but then we noticed that randomly now it seems to automatically be 5 minutes behind.

For example, if we run the query and use “query {picks_per_day(date_from:“2021-06-25T16:58:50”)”, it will really do it from about 5 minutes and 70 seconds before that (so it would be as if we had entered “T16:52:40”.

Do you know this can be fixed? Or if this was an intentional change by the engineers, do you know the exact seconds that it is behind for that query so we can factor that into our request. Thank you!

If it is helpful, this is an example of a request_id where you can see this (the query was date_from: 19:08:51 but the response has results from before that time (i.e. 19:06:19) :

  • request_id = 60d62a0bd5f24b48a71ec81e
1 Like