Cannot mass update Qty values

[TomMartensNL]

Preconditions (*)

1. Magento version: 2.3.4
2. Using 296.124 items (13.584 configurable + 282.533 simple products) for a store

Steps to reproduce (*)

1. Use admin backend and head over to Catalog --> Products
2. Select all products using the selector in a product grid (top left) and click on 'Select All'
3. Select 'Actions' --> 'Update Attributes'
4. Head over to 'Advanced Inventory' (side menu left) and enable 'change' for 'Qty' field
5. Set 'Qty' value to 999999
6. Press 'Save'

Expected result (*)

1. Notification with 'Message is added to queue'
2. Selected items have their quantities updated to 999999 after some time

Actual result (*)

1. After around 20 minutes of processing the browser gets back HTTP 500 error from Magento.
2. Not all products have their updated quantity. A chunk of these products do have a new quantity value, but, by far most don't.

Additional information

From what I've found searching the source code, here are some interesting findings:

• Inventory changes don't use to functionality of other bulk update operations. This specific operation will execute when a user presses 'Save'. It loops through all productIds and tries to update its inventory, one by one: https://github.com/magento/magento2/blob/2.3/app/code/Magento/CatalogInventory/Plugin/MassUpdateProductAttribute.php#L145

• Other attributes like website/store assignments do, in contrast to inventory attributes, use a bulk update in combination with Magento2 consumers: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Catalog/Controller/Adminhtml/Product/Action/Attribute/Save.php#L231

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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]

Hi @TomMartensNL. 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

[m2-assistant]

Hi @engcom-Oscar. 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: 👇

• 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.

[TomMartensNL]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @TomMartensNL. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @TomMartensNL, here is your Magento Instance: https://d3979af6c53f7c8170de83a52ef6e26d-2-4-develop.instances.magento-community.engineering
Admin access: https://d3979af6c53f7c8170de83a52ef6e26d-2-4-develop.instances.magento-community.engineering/admin_b5a6
Login: 17ac687b
Password: c1b26d5f26ba

[magento-engcom-team]

✅ Confirmed by @engcom-Oscar
Thank you for verifying the issue. Based on the provided information internal tickets MC-42073 were created

Issue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[sandy6666]

@magento I am working on this

[sandy6666]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @sandy6666. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @sandy6666, here is your Magento Instance: https://d3979af6c53f7c8170de83a52ef6e26d-2-4-develop.instances.magento-community.engineering
Admin access: https://d3979af6c53f7c8170de83a52ef6e26d-2-4-develop.instances.magento-community.engineering/admin_d767
Login: bc5d806b
Password: 6ded57de7b21

[sandy6666]

@magento this issue is not reproducable.
The update worked properly in the above instance given

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://7b6dc982ff6fc4933524043874eb9435.instances-prod.magento-community.engineering
Admin access: https://7b6dc982ff6fc4933524043874eb9435.instances-prod.magento-community.engineering/admin_9d5e
Login: e1bdc584
Password: 5bf40e7fbfc8

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 2. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[engcom-Delta]

Hi @TomMartensNL ,

Thanks for your reporting and collaboration.
We have verified the issue in 2.4 develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.
Tested issue with 3000 products in catalog.

Steps to reproduce

1. Use admin backend and head over to Catalog --> Products
2. Select all products using the selector in a product grid (top left) and click on 'Select All'
3. Select 'Actions' --> 'Update Attributes'
4. Head over to 'Advanced Inventory' (side menu left) and enable 'change' for 'Qty' field
5. Set 'Qty' value to 999999
6. Press 'Save'

7. Notification with 'Message is added to queue'

8. Observe Qty is updated for all simple products.

Can you please re-verify in 2.4 develop instance and confirm.

Thanks.

[engcom-Delta]

Hi @TomMartensNL ,

This issue is being closed since it has not been updated in a long time.
Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.