Orders -> created_at_min ignored

Solved
New Member
1 0 3

In the past 72 hours, we noticed that created_at_min started to have no effect. I also found a new question on Stack Overflow with the same issue.

 

e.g. GET https://[storename].myshopify.com/admin/api/2019-04/orders.json?created_at_min=2019-08-08T08:00:00-07:00 is returning orders since midnight store time (which is 2019-08-08T01:00:00-07:00).

 

How do we report potential issues like this, and is anyone else seeing the same behavior?

3 Likes
Tourist
3 0 0

We're noticing a similar issue with created_at_max. We have a query like:

 

https://{redacted}.myshopify.com/admin/orders.json?created_at_max=2019-08-03T15%3A22%3A00-04%3A00&limit=1&status=any.

 

The created_at attribute for the order in the response is "2019-08-03T23:37:41-04:00", which is after created_at_max.

0 Likes
New Member
2 0 2

We're experiencing the same issue as well, which is breaking our warehouse API integration. Any word on a fix for this?

1 Like
Pathfinder
125 4 23

Wast just about to post something similar, got reports from 2 customers of our app about it today.  Seems to be working fine for most stores (for now) and I tested on 2 of our test stores and still fine there as well.

 

For one customer, it started happening on Aug 7 looking at the logs.  Another customer it just started happening a few hours ago.

 

The date seems to be working but not the time (though there seems to be an issue with calculating based on timezone as well).

 

Here's an output from our tests:

 

---

>>> Current Time UTC: 2019-08-12 20:23:23.162581

 

>>> Order Count from 2019-08-12T00:00:00.273557+00:00: 33
>>> Order Count from 2019-08-12T23:59:59.273557+00:00: 13

 

>>> Testing New York Timezone -04:00

 

>>> Order Count from 2019-08-12T00:00:00.273557-04:00: 13
>>> Order Count from 2019-08-12T23:59:59.273557-04:00: 13

 

---

 

Notice that even if the time is set in the future, orders are still being returned.

2 Likes
New Member
2 0 2

What's strange is that the orders/count.json endpoint is recognizing these parameters, but the orders.json endpoint is not. 

1 Like
Pathfinder
125 4 23

Just had another customer report the same issue, so 3 separate stores now :(.

 

I'm wondering if Shopify is slowly rolling out a change to stores that's causing this...

 

Just to provide more info, our app is using API version 2019-04 (which shouldn't get any API updates, which makes it weird this is happening).

 

We've contacted Shopify as well via the Shopify Partners dashboard and I'll post an update here once we hear back from them.  Hopefully, this will get fixed soon before more stores start having the issue as this is a pretty serious bug and affecting our customers' fulfillment processes.

2 Likes
Pathfinder
125 4 23

Just got another report again today and for this store it just started happening a few hours ago.

 

I'm worried there's some change that's being rolled out slowly that's causing this and now getting pushed out to bigger batches of stores.

 

@Josh Any ideas about this?

0 Likes

Success.

Shopify Staff
Shopify Staff
551 50 107

Hey there, everyone!

 

Bo here from Shopify Support.

 

Our technical team has just reached out to let us know that we have rolled back a change that would have caused this and now, everything is working again. If you experience any further problems please do reach out to our team via chat or email so that we can investigate this for you.

 

All the Best,

Bo

Bo | Social Care @ Shopify
 - Was my reply helpful? Click Like to let me know! 
 - Was your question answered? Mark it as an Accepted Solution
 - To learn more visit the Shopify Help Center or the Shopify Blog

4 Likes