Caching Experience Fragments
Published
Experience Fragments (XF) often face cache invalidation issues, where modifying and publishing an XF does not update
the pages referencing it because the XF content is cached within each individual page rather than a shared repository. As a result,
authors have to manually activate or invalidate each page to see the updated XF content, making the process tedious and impractical.