ACSD-47937: Customers are not getting product price drop email for subsequent product price changes

Categories

Emails

Components

b/c, magento/framework, magento/framework-amqp, magento/module-elasticsearch, magento/module-product-alert

Origin

adobe-commerce-support

Since QPT

1.1.26

Issue

Customers are not getting product price drop email for subsequent product price changes.

Steps to reproduce

1. Enable Product Alert for both Price Changes and Back in Stock in Store > Configuration > Catalog > Product Alert. 1. Enable Display Out of Stock Products. 1. Create a simple product (ABC) with qty = 0. 1. Create a customer from the storefront and subscribe to the above product to get product alerts for price drops. 1. Start the product alert for customers. bin/magento queue:consumers:start product_alert 1. Drop the price for the ABC product. 1. Trigger the product alert cron. php n98-magerun2.phar sys:cron:run catalog_product_alert 1. Drop the price for the ABC product again. 1. Trigger the product alert cron. php n98-magerun2.phar sys:cron:run catalog_product_alert >[!NOTE] > >If you are not familiar with n98 tool, then you can run bin/magento cron:run command as usual and monitor cron_schedule table to make sure catalog_product_alert job gets success status.

Adobe's page lists 2.4.4, 2.4.5, and 2.4.5-p1 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.4.6.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACSD-47937. On Cloud, add ACSD-47937 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACSD-47937/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.

Patch files and compatible versions

Sources

• Adobe documentation for ACSD-47937
• JSON API: /api/v1/patches/ACSD-47937