API Feed updates every few minutes, need to bust cornerstone builder's page cache

Support
#1

I’m running into an issue where the page is caching within the Pro/Cornerstone framework for too long. The API feed updates every few minutes at times, but the page itself appears to hold the cache for hours after an update is in place. The only way I can seem to immediately break it is by clicking on CS > Settings > Clear Cache or saving the page with the updated content (clearing the cache).

There needs to be some type of internal mechanism that can handle this. Maybe there is and I’m not finding it in the API dev docs?

Is there a CLI command I can use to flush cache on specific pages?

#2

Hey @splaquet,

Thank you for reaching out. I understand your API feed refreshes every few minutes, but the Cornerstone page keeps showing older data for hours, and you are looking for a way to flush the cache for specific pages. Please review the steps below to resolve this.

  1. Lower the Cache Time on your API Looper Provider – open the element that holds the Looper Provider (API), find the Cache Time setting, and set it in seconds to match how often your feed updates (for example, 60–300). Leaving it empty disables caching entirely. If you started from the RSS Feed prefab, note that it ships with a Cache Time of 21600 seconds (6 hours), which matches the “hours” delay you are seeing.

  2. Understand what the cache is – Cornerstone stores each API response as a file keyed by the endpoint and its request arguments, and treats it as expired once its age exceeds the Cache Time. It is not stored per page, so there is no per-page flush; clearing it is global. Saving a page only refreshes style data and does not remove stored API responses, and wp cs clear_style_cache clears the style cache only, so neither will reset the feed. The cache-clearing option in Cornerstone Settings is the one that does clear stored API responses.

  3. Rule out a second caching layer – if the delay continues after lowering Cache Time, exclude the page from any page-caching plugin, host-level cache, or CDN (or give it a short expiry), then test while logged out in a private browser window.

Cheers.