DocumentationCommerceTools

[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

ACSD-63687: Incorrect prices are displayed due to Redis cache cleanup issues

Last update: Fri Feb 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACSD-63687 patch fixes the issue where incorrect prices display when the Redis cache garbage collector runs without LUA mode, causing race conditions. This patch is available when the Quality Patches Tool (QPT) 1.1.77 is installed. The patch ID is ACSD-63687. 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.5-p9

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.5 - 2.4.6-p13
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the 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

Incorrect prices display because Redis cache cleanup fails.

Steps to reproduce:

  1. Configure Redis for the Adobe Commerce environment.

  2. Create multiple product categories in the storefront.

  3. Create a script that sends recurring requests to a category page. Use a JMeter script or an equivalent load‑testing tool.

  4. While the script sends requests to the category page, perform a block_html cache clean and run the backend_clean_cache cron job multiple times.

  5. Execute the provided script to identify Redis cache key records that don’t exist in the MAGE cache set. Update the Redis port and MAGE cache tag prefix to match the local project configuration.

    code language-none 
    #!/bin/bash

REDIS_PORT=6379
REDIS_DB=0
SET_NAME="zc:ti:af6_MAGE"

redis-cli -p $REDIS_PORT -n $REDIS_DB keys "zc:k:*" | while read KEY; do
  STRIPPED_KEY=${KEY#"zc:k:"}
  EXISTS=$(redis-cli -p $REDIS_PORT -n $REDIS_DB sismember "$SET_NAME" "$STRIPPED_KEY")

  if [ "$EXISTS" -eq 0 ]; then
    TIMESTAMP=$(redis-cli -p $REDIS_PORT -n $REDIS_DB hget "$KEY" "m")

    if [ -n "$TIMESTAMP" ]; then
      FORMATTED_TIME=$(date -r "$TIMESTAMP" +"%y-%m-%d %H:%M:%S")
      echo "$KEY - m: $FORMATTED_TIME"
    else
      echo "$KEY - m: (null)"
    fi
  fi
done

Expected results:

Cache keys without corresponding records are not created in Redis, and the backend_clean_cache Cron job cleans cache entries correctly.

Actual results:

Cache keys are created in Redis without corresponding records, so cache cleanup triggered by the backend_clean_cache cron doesn’t work.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3