Configurable product is not obtained when stock change from out of stock to in stock

[hhonetree]

Preconditions and environment

• Magento 2.4.4-p1

• Using: "magento/module-upward-connector": "^2.0" "magento/pwa": "^0.3.0"

-Used GraphQl:

{ products(
filter: { url_key: {eq: "config" } } ){ items{ uid name sku url_key } } }

Steps to reproduce

I have Magento 2.4.4 installed in the cloud and the problem is when you change configurable product stock in this order:

1. Create configurable product In Stock
2. Update child product Qty 0 and Out of stock
3. Update child product Qty 100 and In Stock

Expected result

Get product to show up in GraphQl search or catalog/search.

Actual result

The product detail admin shows "In Stock", but it still doesn't show up in catalog/search or GraphQl search.

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @hhonetree. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

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

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

:clock10: You can find the schedule on the Magento Community Calendar page.

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

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

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hi @hhonetree Thank you for reporting. Verified the issue on Magento 2.4-develop branch but the issue is not reproducible. After changing the stock status from out of stock to instock and with quantity - product is searchable in both front end and graphql as well. Kindly recheck the behavior on Magento 2.4-develop instance and provide missing steps if any if the issue is still reproducible. Thank you.

[engcom-November]

Hi @hhonetree , We are closing this issue as there has been no latest update on the same. Kindly reopen / create new issue if you are still facing any issues. Thank you.

[davirs]

I have the same problem here with magento version 2.4.4 with php 8.1. The products work correctly and randomly some entire category of products or specific products are simply marked in the display as "out of stock". Both configurable and simple products are correct and stocked, it's just in the frontend display that has this bug.

Here I also have the problem that was mentioned above, when the product is sold and has zero saleable quantity it keeps appearing on the frontend as if it was in stock...

Really are 2 extremely serious bugs because they disturb sales and generate numerous complaints daily.

If anyone has an alternative solution I would be very grateful!