Products positions are not updated in GraphQL query result

[magento-engcom-team]

Precondition

Use GET to submit GraphQL query in order for query result to be cached. see GraphQL Caching

Steps to reproduce

1. Create at least 2 products
2. Create category and assign products created in step.1 and save category
3. Execute the query below
4. Check that products are ordered correctly
5. Change products positions in the category and save changes
6. Execute the query below

Query

query getProducts { 
  products( 
    filter: {
      category_id: 
        { eq: "<category ID>" } 
    } 
    sort:
    	{position:ASC} 
  ) 
  { 
  total_count 
    items { 
      name 
      sku 
    } 
    page_info { 
      page_size 
      current_page 
    } 
  } 
}

(x) Actual result

Products positions are not updated.

(/) Expected result

Products positions are updated.

(i) Notice

This issue is reproducible only if GraphQL query result is cached. the cache is not invalidated when products positions changed within a category. However this works with regular category page (PLP).

[magento-engcom-team]

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/MC-38078

[m2-assistant]

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[Zifius]

@magento I am working on this