---
schema_version: "1"
id: b4a83b1fa002285dd560d55c361f3f126f309eebea3c0a13fa51321c8cd31c9a
title: Future Dated Cache
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries/cme/guides/comms-t-future-dated-cache.md
canonical_url: https://developer.salesforce.com/docs/industries/cme/guide/comms-t-future-dated-cache.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: d727dcc83e039e43d6f1c3dc84259a0567d0f762f8f0c1a62f84cae6d22573e7
products:
  - Communications, Media, Energy and Utilities APIs (Managed Package)
  - Industries Developer Documentation
---
# Future Dated Cache

The Future Dated Cache feature allows you to enter the date and time when you want the cached records to become effective.

For example, suppose you update your product catalog on March 31 but want the updates to become effective at midnight on April 1st. Setting the date and time to 12:00 a.m. on April 1 updates the cache data so that subsequent to the effective date, API calls retrieve the updated cached data.

When the job is run, the following window displays:

![Regenerate Cached API Records](https://developer.salesforce.com/docs/media/regen_cached_records.png)

**note:** You must set CacheAPI.RegenerateFutureDatedCache=true for the Regenerate Cached API Records window to display. See [CPQ Configuration Settings Reference](https://help.salesforce.com/s/articleView?id=ind.comms_t_cpq_configuration_settings_reference_148927.htm&type=5).

When the Regenerate Cached API Records batch job is run with a selected date, it can only be rerun on or after that specified date and time. See [Regenerate Cache Batch Process Examples and Best Practices](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-regenerate-cache-batch-process-examples-and-best-practices.md).

**important:** The Regenerate Cache batch job does not support the Future Dated Cache feature when Product Versioning is enabled.