From fe7caecf616ee02c0622623103a406e9c19869ca Mon Sep 17 00:00:00 2001 From: Umut Dogan Date: Fri, 9 Jan 2026 16:24:38 +0100 Subject: [PATCH] document info-level logging for cache invalidation --- concepts/framework/http_cache.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/concepts/framework/http_cache.md b/concepts/framework/http_cache.md index 62a917abc..8e034393b 100644 --- a/concepts/framework/http_cache.md +++ b/concepts/framework/http_cache.md @@ -94,6 +94,8 @@ For more information about Store API cache invalidation, you can refer to the [C This is because all data loaded in a Storefront controller is loaded in the core via the corresponding Store API routes and provided with corresponding cache tags. So the tags of the HTTP cache entries we have in the core consist of the sum of all Store API tags generated or loaded during the request. Therefore, the invalidation of a controller route is controlled over the Store API cache invalidation. +Cache invalidations are logged at the info level to improve observability. + ## HTTP Cache workflow **Note:** Workflow described here applies since v6.8.0.0 or since 6.7.6.0 when the `CACHE_REWORK` feature flag is enabled.