Content staging does not update coupon codes when related Rule's coupon setting is "Auto" (Magento_Reminder)

[TheBadong]

Preconditions and environment

• Adobe Commerce 2.4.6-p8
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Create a new cart price rule
2. Set the rule to Active
3. Set the "coupon" setting to "Auto" <- ONLY Available with the Magento_Reminder module installed (not a third party)
4. Save the rule
5. Generate a few coupon codes using the form under "Manage coupon codes"
6. Using Content Staging, schedule a new update in a few minutes. In this update, disable the rule
7. Wait for the update to apply

Expected result

The generated coupons should see their expiration_date field updated in the database, and no error logs should be generated.

Actual result

The coupons are not updated and an error pops up in var/log/debug.log : "An error occurred during processing; coupon with id expiration date wasn't updated. The error message was Specified rule does not allow auto generated coupons".

Additional information

I'm not sure why the Auto option for the coupon settings is added by the Magento_Reminder module. See \Magento\Reminder\Observer\GetCouponTypesObserver. Maybe this should be mentioned in the module's README.

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 @TheBadong. 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.