ACP2E-4706: Target Rule indexer cron doesn’t pick products enabled only at store view scope
The ACP2E-4706 patch fixes the issue where the Target Rule indexer cron doesn’t pick products that are enabled only at a store view scope, causing products not enabled in the Adobe Commerce Admin scope to be skipped. This patch is available when the Quality Patches Tool (QPT) 1.1.79 is installed. The patch ID is ACP2E-4706. Please note that this issue is scheduled to be fixed in Adobe Commerce 2.4.9.
Affected products and versions
The patch is created for Adobe Commerce version:
- Adobe Commerce (all deployment methods) 2.4.8-p3
Compatible with Adobe Commerce versions:
- Adobe Commerce (all deployment methods) 2.4.5 - 2.4.8-p4
magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.Issue
The Target Rule indexer cron doesn’t pick products that are enabled only at a store view scope, causing products not enabled in the Adobe Commerce Admin scope to be skipped by the indexer.
Steps to reproduce:
- Create a simple Related Product Rule.
- Create a product that is disabled at the Admin (global) scope but matches the rule conditions. (the rule can be kept simple by not adding any conditions under Products to Match or Products to Display).
- Run the cron to execute the indexer backlog.
- Edit the product and switch to the Default Store View scope.
- Enable the product only at the Default Store View scope.
- Run the cron to execute the indexer backlog.
- Check the Storefront on a different product for the Related Products section, or query the
magento_targetrule_producttable to verify that the newly created product ID exists.
Expected results:
The product should be added to the Related Product Rule (magento_targetrule_product table) by the indexer cron when created as disabled, and enabled only at the store view scope.
Actual results:
The indexer cron does not pick the product and add it to the Related Product Rule (magento_targetrule_product table).
The product is added to the backlog of the targetrule_product_rule_cl table, but the indexer skips it during processing because it is enabled only at the store view scope.
Apply the patch
To apply individual patches, use the following links depending on your deployment method:
- Adobe Commerce or Magento Open Source on-premises: Quality Patches Tool > Usage in the Quality Patches Tool guide.
- Adobe Commerce on cloud infrastructure: Upgrades and Patches > Apply Patches in the Commerce on Cloud Infrastructure guide.
Related reading
To learn more about Quality Patches Tool, refer to:
- Quality Patches Tool: A self-service tool for quality patches in the Tools guide.