Error while creating a scheduled update for bundle product within store view scope

[gnumus]

Preconditions and environment

• Magento version: EE 2.4.6-p3
• 2+ websites, stores, store views
• Price scope: website
• Have a bundle product with Dynamic price "On" (can be reproduced using the bundle from sample data)

Steps to reproduce

In admin area:

• Open the bundle product for editing
• Switch to a store view scope
• Click "Schedule new update"
• Set title and time for the update
• Some product attributes can be changed (however, I can reproduce with no changes in attributes)
• Click "Save"

Expected result

Product's content change is scheduled

Actual result

An error message "Could not save child" appears, please see screenshot

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 @gnumus. Thank you for your report. To speed up processing of this issue, 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.

[m2-assistant[bot]]

Hi @engcom-Bravo. 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).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

[m2-assistant[bot]]

Hi @engcom-Dash. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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!

---

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

[engcom-Dash]

Hi @gnumus

Thanks for reporting and collaboration. Verified the issue in magento developer instance and the issue is not reproducible. The products content change is getting scheduled. we are not seeing the error while creating a schuduled update for bundle products. Please refer the screenshots.

[gnumus]

Hi @engcom-Dash

Could you please make sure that you have several websites on your instance, price scope is set to "Website":

I recorded a video with the bug on clear 2.4.6-p3 + Sample data:

https://github.com/magento/magento2/assets/22933058/6c785f8c-ca1c-4f1b-bcba-b6abe1ec242e

Thanks

[engcom-Dash]

Hi @gnumus

Thanks for reporting and collaboration.

Verified the issue on magento dev instance but the issue is not reproducable.

As per the previous comment we have set the price scope to website and tried to schedule update. Able to schedule update for a bundle product successfully.

Please refer the attached screen recording.

https://github.com/magento/magento2/assets/60198592/3d845dc7-86b8-466f-bc9b-7aec811840a6

[engcom-Dash]

Hi @gnumus

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.