Keep CDN Content Fresh Across Every Edge Server
When your content changes but the CDN keeps serving the old version, users see stale data. CronJobPro triggers your CDN purge API on schedule, ensuring fresh content reaches every edge location reliably.
Stale CDN Content Frustrates Users and Breaks Experiences
CDN caching is essential for performance, but when content updates, the CDN keeps serving outdated assets. Manual purges are forgotten, and API-based purges need automation to be reliable.
- ✗Marketing updated the homepage banner but the CDN keeps serving the old image for hours
- ✗Developers manually purge the CDN after deploys and sometimes forget critical paths
- ✗No verification that a CDN purge actually propagated to all edge locations
- ✗Multi-CDN setups require purging multiple providers — easy to miss one
Automated Purges Across All Your CDN Providers
CronJobPro triggers your CDN purge endpoint on a defined schedule. Whether you use Cloudflare, CloudFront, Fastly, or multiple providers, every purge is executed, verified, and logged.
REST API
Programmatically create purge jobs through the CronJobPro API — perfect for adding purge schedules as part of your deployment pipeline.
Automatic Retries
CDN APIs occasionally return rate-limit errors. CronJobPro retries with backoff, ensuring the purge completes even during high-traffic periods.
Execution Logs
Every purge is logged with the CDN API response, so you can verify propagation and troubleshoot when content remains stale.
How to Set It Up
- 1
Create a purge endpoint that calls your CDN API
Build an HTTP endpoint that triggers the purge API for your CDN provider (Cloudflare, CloudFront, Fastly, etc.) and returns the purge status.
- 2
Add the purge endpoint as a cron job
Set the purge job URL in CronJobPro with appropriate authentication headers for your CDN API.
- 3
Schedule purges based on content update frequency
E-commerce sites with frequent product updates might purge every 15 minutes. Content sites might purge hourly or after each deploy.
- 4
Verify purge propagation with monitoring
Set up a follow-up monitoring job that checks a known URL after the purge to verify the CDN is serving updated content.
Recommended Schedules
| Expression | Schedule |
|---|---|
| */15 * * * * | Purge CDN every 15 minutes for dynamic content |
| 0 * * * * | Hourly CDN cache refresh |
| 0 5 * * * | Daily full CDN purge at 5 AM |
Start Automating Now
Set up scheduled cdn cache purge in under 2 minutes. Free forever for up to 5 jobs.
Frequently Asked Questions
Which CDN providers can I purge with CronJobPro?
Any CDN that offers a purge API — Cloudflare, AWS CloudFront, Fastly, Akamai, KeyCDN, BunnyCDN, and more. Your endpoint calls the CDN API; CronJobPro triggers your endpoint.
How do I purge specific URLs instead of the entire CDN cache?
Build your purge endpoint to accept URL paths or patterns in the request body. CronJobPro can send POST requests with a JSON payload specifying exactly what to purge.
What if I use multiple CDN providers?
Create a single endpoint that calls all your CDN purge APIs in sequence, or create separate CronJobPro jobs for each provider. Both approaches work — choose based on your error handling preferences.
Will frequent purges hurt my CDN performance?
Purging too aggressively increases origin load as the CDN rebuilds its cache. Balance purge frequency with your content change rate — purge only what needs refreshing, not everything.
Related Use Cases
Scheduled Cache Invalidation
Stale caches serve outdated data to your users while manual purges are tedious and easy to forget. CronJobPro automates cache invalidation on a precise schedule so your content stays fresh and your team stays focused.
Website Uptime Monitoring
CronJobPro pings your website on a schedule you define and alerts your team the moment something goes wrong. With automatic retries and multi-channel notifications, you catch outages before they cost you customers.
Scheduled Server Maintenance
Server maintenance is critical but repetitive. CronJobPro triggers your maintenance endpoints on schedule — clearing temp files, restarting services, checking disk health — so your infrastructure stays reliable without manual effort.