Use Cases
Scheduled Cache Warming and Invalidation
Automate cache refresh and invalidation on a cron schedule. Keep your CDN, Redis, or API cache fresh with TrigRun scheduled HTTP calls.
Keep your caches fresh by hitting your invalidation or warming endpoint on a schedule. No stale data, no manual purges, no cron server to maintain.
The problem
Your application caches expensive queries, CDN content, or API responses. Caches go stale, but you don't want every user request to trigger a cache rebuild. You need a scheduled refresh — and if it fails, you need to know immediately.
The TrigRun solution
| Setting | Value |
|---|---|
| Schedule | */15 * * * * (every 15 minutes) |
| Method | POST |
| Timeout | 60 seconds |
| Retries | 2 attempts |
Create via API
Common patterns
CDN cache purge
Redis cache refresh
Common schedules
| Pattern | Expression | Use case |
|---|---|---|
| Every 5 minutes | */5 * * * * | Real-time leaderboards, pricing |
| Every 15 minutes | */15 * * * * | Product catalogs, search indexes |
| Every hour | 0 * * * * | Dashboard data, analytics |
| Every 4 hours | 0 */4 * * * | CDN purge, full rebuild |