Config changes invalidating cache
Dispatcher Flush Rules are intended to be deployed and executed on AEM Publish, which should have On Trigger Flush Agents set up.Running Dispatcher Flush Rules on AEM Author that flush Dispatchers for AEM Publish can result in race-conditions, where the Dispatcher cache invalidation (and re-caching of content) can occur prior to the new replicated content being persisted on AEM Publish.Define simple, yet powerful, rules for targetted flushing of files cached by Dispatcher.Dispatcher cache flushing is typically done by setting a stat level, which means a piece of content changes at a certain “folder level” in the cache, then everything under that folder (or a relative folder level) is invalidated.As a rule of thumb it would help understanding cache variations if you imagine each unique variation of the page URL as a separate output cache item.Each variation is stored in output cache as a separate item with unique key, however all variations of the page use a single page compilation.This way Sitefintiy CMS always keeps an up-to-date version of all items in the cache.
Create a new Dispatcher Flush Rules work from AEM 5.6 Publish Servers as well.
By default, when a cached version of a page is created, this version is tied to a number of dependency objects - like the content items displayed on the page, or the page template.
Editing any of the dependencies causes the cached version of the page to be invalidated.
By default, the cache version of the page is recorded using the page base URL.
However, when you want to view the details of a content item on the page, the page HTML changes, and it makes sense to cache this version of the page as a separate item in output cache using a new key - the content item URL (the combination of the page base URL and the content item URL name). Each page can have multiple cache variations, depending on whether it has content items that can be displayed in details on it, and any paging or filtering that is applied to the widgets on the page.