---
schema_version: "1"
id: 84458fab32e508bf600497b8a036b85638d03399425e18ad70ed238939419ab7
title: Regenerate Catalog-Level Cache Data
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries/cme/guides/comms-t-regenerate-catalog-level-cache-data.md
canonical_url: https://developer.salesforce.com/docs/industries/cme/guide/comms-t-regenerate-catalog-level-cache-data.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 9fac7421a26e925d1ddaafaa26b3d47dca7a3067090e60fb5d37e88b8cb86ead
products:
  - Communications, Media, Energy and Utilities APIs (Managed Package)
  - Industries Developer Documentation
---
# Regenerate Catalog-Level Cache Data

These batch jobs populate the catalog-level data in the cache. In the cached API change table, the system queries any unprocessed change object of code type as catalog present or not. For the unprocessed catalog change entries, the catalog level batch jobs dataProfile, eligibility, and getOffers run.

With versioning enabled, additional catalog version information included, and derivations that include timeSlice as the affected entity, the batch job gets the catalog grouped by the affected time slices that were populated during the Derive Entity batch job. For those time slices, the effective time slice date of the first time slice and the effective time slice end date of the last time slice for that catalog become the boundary effectivity time. For example, the boundary effectivity time can consist of the cache effective start and end times for which the version info generator batch job ran and created new time slices, versionInfo, and time slice info cache data. The subsequent batch jobs, dataProfile, eligibility, and getOffers, use the same cache effective start and end times as its boundary. Those batch jobs also use the new time slice information generated by the version info generator as the time slices on which to operate and cache the corresponding data.