GraphQL addWishlistItemsToCart Fails to Update Quantity for Existing Cart Items When One Wishlist Item Is Invalid (Magento 2.4.7-p3)

[lintots]

Preconditions and environment

• Magento version: 2.4.7-p3
• GraphQL enabled
• Default Magento Luma theme or similar
• Wishlist and Cart modules enabled

Steps to reproduce

1. Create a simple product and a configurable product (with required options).
2. Add the simple product to the cart with quantity = 1.
3. Add the configurable product to the wishlist, but do not select options.
4. Add the same simple product to the wishlist.
5. Use the GraphQL mutation addWishlistItemsToCart to try to add all wishlist items to the cart:
   mutation {
   addWishlistItemsToCart(
   wishlistId: "wishlistid"
   wishlistItemIds: [])
   {
   status
   add_wishlist_items_to_cart_user_errors {
   code
   message
   }
   wishlist {
   id
   items_v2 {
   items {
   id
   product {
   uid
   sku
   name
   }
   }
   }
   }
   }
   }

Expected result

• The mutation should:
  - Add the simple product to the cart again, updating its quantity from 1 → 2.
  - Skip the invalid configurable product and include its error in the add_wishlist_items_to_cart_user_errors array.
  - Return a success status and updated wishlist info.

Actual result

• The mutation fails early due to the invalid configurable product (missing required options).
• The simple product's quantity is not updated in the cart.
• The process halts on the first failure instead of continuing with other valid wishlist items.

Additional information

• The issue occurs only if a configurable product with missing required options appears before valid items in the wishlist.
• For example:
  1. A simple product (e.g., simple-sku) is already in the cart with quantity 1.
  2. The same simple product is also added to the wishlist.
  3. A configurable product (with required options not selected) is added to the wishlist before the simple product.
  4. When calling addWishlistItemsToCart, the configurable product causes an exception (REQUIRED_OPTIONS_MISSING), which halts the mutation execution.
  5. As a result, the simple product below it in the wishlist does not get processed — its quantity in the cart is not updated.
• If the invalid configurable product is placed after the valid product in the wishlist item list, then the valid product gets processed first and is updated in the cart, but the configurable product still throws an error (as expected). So the order matters.

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]

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

• 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.
⚠️ 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, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

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: 👇

• 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

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

Hi @lintots,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in latest 2.4-develop instance and we are able to reproduce the issue.kindly refer the screenshots.

• The mutation fails early due to the invalid configurable product (missing required options).
• The simple product's quantity is not updated in the cart.

Hence Confirming the issue.

Thanks.