Cloudflare Workers Cron Triggers

Gotchas

• 100,000 Worker requests/day

  The free plan allows up to 100,000 total Worker invocations per day, shared across all Workers including Cron Trigger executions; resets daily at 00:00 UTC.

• 10 ms CPU time per invocation

  Each free-tier Worker invocation is capped at 10 milliseconds of CPU time, making it unsuitable for compute-heavy scheduled jobs.

• No Durable Objects on free tier

  Durable Objects (used for stateful or long-running cron workflows) require the Workers Paid plan; free tier supports SQLite-backed DO only with its own daily limits.

• No Logpush on free tier

  Workers Trace Events Logpush (for exporting execution logs to external destinations) is only available on the Workers Paid plan.

• Log retention 3 days only

  Free plan Workers Logs are retained for only 3 days (vs. 7 days on Paid), limiting post-mortem debugging of scheduled jobs.

• 200,000 log events/day

  Free plan allows 200,000 Workers log events written per day; cron-heavy workloads with verbose logging may exhaust this.

• Workers KV: 100K reads/day, 1K writes/day

  KV reads are capped at 100,000/day and writes at 1,000/day on the free plan; cron jobs that store state in KV will hit write limits quickly.

• Workers KV: 1 GB storage cap

  Free plan includes 1 GB of total KV stored data; no additional storage can be purchased without upgrading.

• Queues: 10,000 operations/day

  Free plan includes only 10,000 Queue operations per day and limits message retention to 24 hours (non-configurable), making it unsuitable for reliable cron-triggered pipelines.

• Shared edge infrastructure

  Free plan Workers run on shared Cloudflare edge infrastructure with no SLA; execution timing for Cron Triggers may drift slightly from the configured schedule.