A cache temporarily stores active data (such as web pages, text, images, and so on) in a dedicated local folder, to shorten data access times and improve performance.

The following table describes the various caches and the events during which they are used.

Cache name


Agent versions

The versions of M.Agent entities used in Media processing.


IDs of M.Agent entities used in Media processing.

Aggregate definition

Temporary files of edits made to aggregate entities, to improve load performance by combining multiple individual calls.

Aggregate definition resource

Entity definitions linked by relations of a specific entity definition.

Channel limit

Applicable limits of content channels.


Temporary files of edits made to Chili publication objects.


Temporary files of edits to menu items (for example, changes to menu or homepage tiles).


Temporary files of edits to M.Notification entities, when sending real-time or email notifications.

Oauth client

OAuth client entities.

Page route map

Website routes, including all the pages and portal languages configured.


Temporary files of edits to the user agreement, or to page components and controllers (for example, when changing the facet tree with the entity manager). Also stores the page view used for constructing a page, which includes the following items:

  • Page data

  • Page layout

  • Page components

  • Component translations (only for KnockOut).

Pages are cached by name and language, whereas detail pages are cached by entity, because different entities can render a different conditional page, such as a video details page for a video asset.


Temporary files of edits to user group policies and security (for example, when the security policies are modified for a specific user group).


A flow template for composite assets, retrieved from settings.


Temporary files of edits to M.RenditionLink entities, used when extracting renditions and watermark information from entities.


Information related to the configuration of search components and filters.


Temporary files of edits to delivery URLs, as well as the settings in the Settings section, cached by category and by name.


Temporary files containing property information. In a hierarchy taxonomy, the parent taxonomy is also stored.


Temporary files related to the import of new portal translations.

User groups

User group names, cached by ID.


User information such as profile details, themes, location, and ID.


Temporary files of edits to watermarks, in a distributed table used to display watermarks from geo-distributed locations.


When you clear a cache, Sitecore Content Hub rebuilds it using data from the database, which may result in a slight dip in performance for anyone using Content Hub at that time.

Do you have some feedback for us?

If you have suggestions for improving this article,