I've noticed that when I install and replicate packages from my Author instance that modify existing files, the cache of the dispatcher does not get invalidated. I understand that I need to create and configure dispatcher flush agents, but when I do, the cache invalidation still does not occur. I think that the cause of this is the same as another of my forums posts , but in that post I'm trying to replicate single files at a time. In this instance, it seems that potentially an entire package of modified content could be installed and replicated, but never used, as the out-of-date cached versions are always used.
Has anyone else come across this before, and if so how did you resolve it?
Based on responses form Adobe in the post linked to above, it would seem that only cq:Page nodes invalidate the cache from a Publish flush agent in CQ5.5. There in a new trigger called 'on receive' in CQ5.6 that does not care about node type and does invalidate the cache as expected.
The solution seems to be create your own triggers/workflows etc and manually create this functionality. An example of how this is done for the DAM assets can be found here .