No reindexing of all indexes during double index invalidate

[KarolLitman]

Preconditions and environment

• Magento version 2.4.7-p4
• Indexes set to Update By Schedule

Steps to reproduce

1. Have a lot of products, for example a few thousand. The rules should take a long time to execute.

2. Go to Marketing->Catalog Price Rule->Enter any rule->Press Save and Apply

3. Go to System->Index Management

In Index Management we have:
Category Products REINDEX REQUIRED
Catalog Rule Product REINDEX REQUIRED
Stock REINDEX REQUIRED
Product Price REINDEX REQUIRED
Catalog Search REINDEX REQUIRED

4. Wait until (not only in this case when this particular indexer processing):

If I had:
Category Products READY
Catalog Rule Product READY
Stock READY
Product Price READY
Catalog Search processing

5. Go to Marketing->Catalog Price Rule->Enter any rule->Press Save and Apply

Cron will go through the next indexes. Catalog Search index is READY.

Category Products REINDEX REQUIRED
Catalog Rule Product REINDEX REQUIRED
Stock REINDEX REQUIRED
Product Price REINDEX REQUIRED
Catalog Search READY

6. The next cron will only execute the Category Products, Catalog Rule Product, Stock, Product Price indexes

Expected result

Catalog Search should be reindexed again

Actual result

Catalog Search has outdated data

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]

Hi @KarolLitman. 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-Delta. 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-Delta]

Hi @KarolLitman ,

Thanks for your reporting and collaboration.
We have tried to reproduce the issue again in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshot.

Steps to reproduce

1. Have a lot of products, for example a few thousand. The rules should take a long time to execute.
2. Go to Marketing->Catalog Price Rule->Enter any rule->Press Save and Apply
3. Go to System->Index Management
   In Index Management we have:
   Category Products REINDEX REQUIRED
   Catalog Rule Product REINDEX REQUIRED
   Stock REINDEX REQUIRED
   Product Price REINDEX REQUIRED
   Catalog Search REINDEX REQUIRED

4. Wait until (not only in this case when this particular indexer processing):
   If I had:
   Category Products READY
   Catalog Rule Product READY
   Stock READY
   Product Price READY
   Catalog Search processing

5. Go to Marketing->Catalog Price Rule->Enter any rule->Press Save and Apply
   Cron will go through the next indexes. Catalog Search index is READY.
   Category Products REINDEX REQUIRED
   Catalog Rule Product REINDEX REQUIRED
   Stock REINDEX REQUIRED
   Product Price REINDEX REQUIRED
   Catalog Search READY

6. The next cron will only execute the Category Products, Catalog Rule Product, Stock, Product Price indexes

Observe, Catalog Search is reindexing as expected.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[engcom-Delta]

Hi @KarolLitman ,

This issue is being closed since it has not been updated in a long time.
Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.