GraphQL. Product tag is cached.

[kushniruk]

Hello, everyone.
I'm having an issue with product tags.
After the update the product tags via API, the graphQL query still works with old product tags.
Only after ~10 seconds, it returns me correct response filtered by a newly added tag.
My query:

 query {
      products(query: "tag:*(my-added-tag)*", first: 10) {
        edges {
          node {
            id
            title
            productType
            images(first: 1) {
              edges {
                node {
                  originalSrc
                  altText
                }
              }
            }
            variants(first: 1) {
              edges {
                node {
                  presentmentPrices(first: 1) {
                    edges {
                      node {
                        price {
                          amount
                          currencyCode
                        }
                      }
                    }
                  }
                  id
                }
              }
            }
          }
        }
      }
  }

Any suggestions? 

Thanks.

[drovani]

Bumping this - hoping someone has been able to find a solution!

We have been running into the exact same problem. There is a 10-45s delay between when we write an update to one or more product's tags using the REST API and when that update is reflected in the results of a GraphQL query.

[RXVTeam]

Same issue. When our client changes shopify tags and then uses our tool to query (by tag) & process orders, they get out of date information!

[patrickb]

Hi all! Did anyone ever get this sorted out?

[drovani]

For our needs, this is still an ongoing problem; we have had to put in wait timers and notices to the user that the data will be updated "soon".

It's a poor user experience, but it's all we have to go off of right now.

[JonathonMinard]

Our integration is running into this too when querying for orders from Shopify.  If a user adds a certain tag to an order we don't want to import the order into our system, but if the user adds the tag and runs our integration within a minute afterwards the order still imports.

[bmcalexander]

This seems to be still a problem. It is in the Orders object as well. Wow, this can cause some serious issues with integrating with ERP system. Duplicate orders are a problem if you use the tag field to mark an order as processed. Hope there is a solution soon. 

Work around, check the tag fields of the returned object for the tag you are looking for or not looking for to be there.