bestsellers monthly and yearly Tables Keep growing due to website deletion

[WebHostingAce]

Preconditions (*)

1. Magento 2.4.3-p1 | Magento 2.4.5-p1, 2.4-develop
2. Multi-Store Setup

Steps to reproduce (*)

1. Place an order in a Multi-Store (both websites)
2. Delete the 2nd website. (Admin - Stores - All Stores - Open Website and delete)
3. Reindex and flush cache
4. Refresh Bestsellers Statistics (Refresh Lifetime Statistics / Refresh Statistics for the Last Day) .
   (Reports - Products - Best Sellers - Click on refresh Statistics link - Select Best Sellers checkbox - Refresh - Submit)
5. Verify DB tables: sales_bestsellers_aggregated_monthly and sales_bestsellers_aggregated_yearly tables
6. Select Best Sellers again and refresh
7. Verify Db tables

Expected result (*)

1. sales_bestsellers_aggregated_monthly and sales_bestsellers_aggregated_yearly tables not to add new entries every time Refresh Bestsellers Statistics (Including the Cron)

Actual result (*)

1. sales_bestsellers_aggregated_monthly and sales_bestsellers_aggregated_yearly tables add new entries every time Refresh Bestsellers Statistics (Including the Cron)

When you have 100,000 orders on the deleted website, this become the real issue.

[m2-assistant]

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

[m2-assistant]

Hi @engcom-November. 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.

[engcom-November]

Verified the issue on Magento 2.4-develop instance and the issue is reproducible. Hence updating the description and confirming the issue.
"sales_bestsellers_aggregated_monthly", "sales_bestsellers_aggregated_yearly" DB tables keep growing after every refresh of Best Sellers due to website deletion.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-7051 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.