hello @agriselli
Any activation (publish) from Author to Publish can trigger cache invalidation if the Dispatcher is configured to invalidate the activated path.
The /cache and /invalidate sections in dispatcher.any define which paths are automatically flushed. Some cache evictions occur only via explicit Dispatcher flush requests, either from AEM or manually (e.g., /dispatcher/invalidate.cache URL or curl).
For most files, Dispatcher marks cache files as stale after an activation; the actual file is refreshed or deleted only when requested again. Files are actively and immediately evicted only if an activation or flush explicitly matches the /invalidate rules.
Also double-check your /invalidate, /invalidateHandler, /statfileslevel, and /enableTTL configuration