cloudflare-cron-triggers

Cron expressions schedule Workers to run at fixed intervals. Add a cron trigger to wrangler.jsonc with five-field syntax (minute, hour, day, month, day-of-week) in UTC, implement a scheduled handler export in your Worker, and deploy with wrangler. The Worker executes automatically on each schedule.

Cloudflare cron triggers use five-field syntax: minute hour day month day-of-week, all in UTC timezone. Configure triggers in wrangler.jsonc under [[triggers.crons]], specify multiple schedules if needed, and ensure your Worker exports a default scheduled handler function to receive trigger events.

Yes, test cron triggers locally using wrangler's --test-scheduled flag, which simulates scheduled execution without deploying. This lets you verify your scheduled handler logic, error handling, and timing behavior before production deployment across environments.

Cron triggers integrate with Cloudflare Workflows to automate recurring tasks. Configure cron schedules in wrangler.jsonc, implement a scheduled handler that invokes Workflow steps, and manage environment-specific cron configurations for different deployment targets.

Common issues include incorrect five-field cron syntax, missing default export of the scheduled handler, timezone mismatches (Cloudflare uses UTC), and ES modules format requirements. Verify wrangler.jsonc configuration, test locally with --test-scheduled, and check handler naming and export structure.

Environment-specific cron triggers deploy different schedules to staging and production by defining separate cron configurations in environment-specific wrangler.jsonc sections. Deploy to target environments with wrangler deploy --env [environment-name] to apply the correct schedule.