SQLSTATE[23000]: Integrity constraint violation: error while running sales_clean_orders cron job

[Usik2203]

Preconditions (*)

I see next error while running sales_clean_orders cron job
SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (magento2.salesrule_customer, CONSTRAINT SALESRULE_CUSTOMER_RULE_ID_SALESRULE_RULE_ID FOREIGN KEY (rule_id) REFERENCES salesrule (rule_id) ON DELETE CASCADE), query was: INSERT INTO salesrule_customer () VALUES ()

Steps to reproduce (*)

1. Set Pending Payment Order Lifetime (minutes) to 1

2. Set schedule for sales_clean_orders to * * * * * in app/code/Magento/Sales/etc/crontab.xml:14
3. Create Cart Price Rule


4. Login as Customer and place order with applied Cart Price Rule

5 Go to sales_order table and set status pending_payment for current order

6 Go Marketing -> Cart Price Rule and remove Cart Price Rule

6 Go to console and run bin/magento cron:run --group="default"

7 Go to cron_schedule table you will see

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (magento2.salesrule_customer, CONSTRAINT SALESRULE_CUSTOMER_RULE_ID_SALESRULE_RULE_ID FOREIGN KEY (rule_id) REFERENCES salesrule (rule_id) ON DELETE CASCADE), query was: INSERT INTO salesrule_customer () VALUES ()

Expected result (*)

I don't see mentioned error while running sales_clean_orders cron job

Actual result (*)

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (magento2.salesrule_customer, CONSTRAINT SALESRULE_CUSTOMER_RULE_ID_SALESRULE_RULE_ID FOREIGN KEY (rule_id) REFERENCES salesrule (rule_id) ON DELETE CASCADE), query was: INSERT INTO salesrule_customer () VALUES ()

Related issues(*)

#27918
#19230
#16779

[m2-assistant]

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

⚠️ 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.

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

[Usik2203]

@magento I am working on this

[tuyennn]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @tuyennn, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[tuyennn]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @tuyennn, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.