404 Error on store front once catalog price rule schedules update is performed

This article provides a patch and the required steps to fix the known Adobe Commerce 2.2.1 issue related to getting a 404 error on all store front pages, after a catalog price rule update was created and its starting time was edited later. To fix the issue you need to apply the patch.

Issue

Storefront pages become unavailable, returning 404 error. The issue appears after the active catalog price rule update becomes due, providing that the starting date of this update was edited after initial creation.

Steps to reproduce:

1. In the Commerce Admin, create a new Catalog Price Rule under Marketing > Promotions > Catalog Price Rule.
2. In the Catalog Price Rule grid, click Edit, schedule a new Update and set Status to Active.
3. Navigate to Content > Content Staging > Dashboard.
4. Select the recently created update and change its starting time.
5. Save the changes.

Expected result :

When the Update start date becomes effective, the catalog price rule is applied successfully.

Actual result :

When the Update start date becomes effective, all catalog and products on the storefront become unavailable returning the 404 error.

Solution

To restore catalog pages and be able to fully use the catalog price rules updates functionality, you need to install the patch, delete the rule both manually and in the admin, and fix the invalid links in the database. You will also need to recreate the catalog price rule.

The following is a detailed description of the required steps:

1. Apply the patch.
2. In the Commerce Admin, delete the catalog price rule related to the issue (where the start time was updated). To do this, open the rule page under Marketing > Promotions > Catalog Price Rule, and click Delete Rule.
3. Accessing the database manually delete the related record from the catalogrule table.
4. Fix the invalid links in the database. See the related paragraph for details.
5. In the Commerce Admin under Marketing, go to Promotions > Catalog Price Rule, and create the new rule with the required configuration.
6. Clear the browser cache under System > Cache Management.
7. Make sure the cron jobs are configured properly and may be executed successfully.

Patch

The patch is attached to this article. To download it, scroll down to the end of the article and click the file name, or click the following link:

Download MDVA-7392_EE_2.2.1_COMPOSER_v2.patch

Compatible Adobe Commerce versions:

The patch was created for:

• Adobe Commerce 2.2.1

The patch is also compatible (but might not solve the issue) with the following Adobe Commerce versions and editions:

• Adobe Commerce on cloud infrastructure 2.2.0 - 2.2.4
• Adobe Commerce on-premises 2.2.0, and 2.2.2 - 2.2.4

How to apply the patch

For instruction, see How to apply a composer patch provided by Adobe in our support knowledge base.

Fix the invalid links to staging in DB

We strongly recommend creating a database backup before any database manipulations. We also recommend testing queries on development environment first.

Take the following steps to fix the rows with invalid links to the staging_update table.

1. Check if the invalid links to the staging_update table exist in the flag table. These would be records where flag_code=staging.
2. Identify the invalid version from the flag table using the following query:

   SELECT flag_data FROM flag WHERE flag_code = 'staging';
   

3. From the staging_update table, select the existing version that is less than the current (invalid) version and get the version value that is two numbers back. You take it, not the preceding version, to avoid the situation when the previous version is the maximum version in the staging_update table that could be applied and we still need to re-apply it.

   SELECT id FROM staging_update WHERE id < %current_id% ORDER BY id DESC LIMIT 1, 1
   

   The version you get in response is your valid version id.
4. For the rows with invalid links in the flag table, set the flag_data values to data which will contain a valid version id. This helps to save performance on reindex step and allows to avoid reindexing all entities.

   UPDATE flag SET flag_data=REPLACE(flag_data, '%invalid_id%', '%new_valid_id%') WHERE flag_code='staging';
   

Example:

SELECT flag_data FROM flag WHERE flag_code = 'staging'; <code class="language-bash">Response < 2.2 version</code>

+-------------------------------------------------+

| flag_data                                       |

+-------------------------------------------------+

| a:1:{s:15:"current_version";s:10:"1490005140";} |

+-------------------------------------------------+

Response from 2.2 version

+-------------------------------------------------+

| flag_data                                       |

+-------------------------------------------------+

| {"current_version":"1490005140"} |

+-------------------------------------------------+

SELECT id FROM staging_update WHERE id < 1490005140 <code class="language-sql">ORDER BY id DESC LIMIT 1, 1</code>;

Response:

1490005138

UPDATE flag SET flag_data=REPLACE(flag_data, '1490005140', '1490005138') WHERE flag_code='staging';

Attached Files