Check if you have invalidated cache

You can find information regarding the invalidated cache types in the <install_directory>/var/log/debug.log file.

To do this:

  1. Open <install_directory>/var/log/debug.log

  2. Search for " cache_invalidate " message.

  3. Then check the tag specified. It indicates what cache was flushed. You might have issues because of the invalidated cache if you see a tag with no particular entity id specified, for example:

    • cat_p - stands for catalog product cache.
    • cat_c - catalog category cache.
    • FPC - full page cache.
    • CONFIG - configuration cache.

    Having even one of them flushed would slow down the response of the website. If the tag contains an entity id, for example, category_product_1258, this would indicate the cache for a particular product or category, and so on. Flushing cache for a particular product or category would not cause response time to drop significantly.

Following is a sample of a debug.log containing records about the cat_p and category_product_15044 cache having been flushed:

sample of the debug.log content

Usually, the cache becomes invalidated because of the following:

  • Full reindex.
  • Flashing cache from CLI, either manually or using cron.

Recommendation

  1. Avoid flushing cache from the Commerce CLI.
  2. Configure indexers to Update by schedule instead of Update on save mode because the latter triggers full reindexing. For reference, see Manage the indexers > Configure indexers in our developer documentation.
Previous pageTurn off hourly Amazon emails when using Adobe Commerce
Next pageGithub token issue and Composer key procedures

Commerce


Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more