DocumentationTools

ACP2E-4448: Configuration changes made during Redis outages do not reflect after Redis recovers, and stale values persist

Last update: May 14, 2026

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACP2E-4448 patch fixes issue where local cache and remote Redis cache could become unsynchronized when Redis is unavailable, and configuration changes made during Redis outages do not reflect after Redis recovers, causing stale values to persist. The fix ensures correct synchronization across all caches and preserves the latest saved values even when Redis is down. This patch is available when the Quality Patches Tool (QPT) 1.1.78 is installed. The patch ID is ACP2E-4448. 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-p1

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.8 - 2.4.8-p4
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

L2 cache, local cache, stale cache, and Redis became unsynchronized when Redis was unavailable. Configuration changes made during Redis outages were not reflected after Redis recovered, causing stale values to persist.

Steps to reproduce:

  1. Configure the L2 cache using the RemoteSynchronizedCache backend with Redis as the remote backend and file cache as the local backend.
  2. Navigate to Configuration > General > Contact > Email Options > Send Emails To.
  3. Update the Send Emails To value to 100@example.com.
  4. Refresh the page multiple times to confirm that the value is cached.
  5. Stop the Redis service to simulate a service interruption.
  6. Update Send Emails To value to 200@example.com.
  7. Start the Redis service.
  8. Refresh the configuration page.

Expected results:

Should show the new configuration value 200@example.com.

Actual results:

It shows the old configuration value 100@example.com.

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
commerce-operations-help-tools