GraphSQL API, sortKey:BEST_SELLING stop working?

[PeterGeorge]

Hi, All.
This one had been working except from today ( edges returns empty ). Simply change the sortKey to "CREATED_AT" would work. 

{
  shop{
    products(first:250, query: "available_for_sale:true AND product_type:>0" , sortKey:BEST_SELLING){
      pageInfo{
        hasNextPage
        hasPreviousPage
      }
      edges {
        cursor
        node {
          id
        }
      }
    }
  }
}

[Kyl]

Hi @PeterGeorge. I don't have a solution for you but just confirming I am experiencing the same issue with the Storefront GraphQL API and seems to have occurred within the past 12 hours.

[poojabokdia]

Hi,
I'm facing the same issue.

[harish-fueled]

Same issue, breaking our app store build, please fix asap

[rdfueled]

We're facing the exact same issue.

We've decided to remove the sort key for now.

[davie-robertson]

removing the sort key is one thing - publishing a new version of the app to work around this (yet to be acknowledged issue) is another.

[rdfueled]

Agreed. We've submitted a new build to the app store earlier today to give us an escape route if Shopify can't resolve the issue quickly.

We also reached out to Shopify Plus support and they weren't aware of the issue but have now escalated. I'll let you know if I hear more.

[PeterGeorge]

Great, I was thinking to reach them today.

I was using a temporary logic for this issue.

So far, it returns data. However, the sorting doesn't sound right compare to previous result.

[rdfueled]

They just reached out asking for full request - body and headers.

That being said, it's working again but they didn't mention having actually done anything.

[Kyl]

While this seems to be working again, the results seem to be identical to sorting products from new to old which is:

sortKey:CREATED_AT, reverse:true

Can anyone else confirm this behaviour?

[PeterGeorge]

I think so. I have reached their customer service yesterday. Look like the issue still there.