WorkerDockFree toolsCloudflare Cron Triggers tester
Cloudflare Cron Triggers tester
Type a cron expression and see what it means, when it will next run in UTC and in your time zone, and how to test it locally. Follows Cloudflare's syntax, where weekdays run 1–7 and 1 is Sunday.
What it means
Next 10 runs
| UTC | Your time |
|---|
Wrangler config
Test it locally
Cron Triggers syntax
| Field | Values | Special characters |
|---|---|---|
| Minute | 0–59 | * , - / |
| Hour | 0–23 | * , - / |
| Day of month | 1–31 | * , - / L W |
| Month | 1–12 or JAN–DEC | * , - / |
| Weekday | 1–7 or SUN–SAT, with 1 = Sunday | * , - / L # |
Cron Triggers always run in UTC. Convert your local time to UTC before writing the expression, or use the time zone box above to see the result in your own time. Cloudflare recommends the three-letter weekday names, because weekday numbers differ between cron systems (many use 0 for Sunday).
What this tool assumes
- Cloudflare's documentation lists
#for weekdays but does not define it. This tool reads2#1the way Quartz does, as the first Monday of the month. - The documentation does not say how day of month and weekday combine when both are set. This tool treats them as "either", like classic cron, and warns you when you do it.
Test a cron locally
While wrangler dev is running, the /cdn-cgi/local/scheduled route triggers your scheduled() handler. If you use the Cloudflare Vite plugin, use the Vite port, 5173 by default, instead of 8787.
Frequently asked questions
Why did my cron run at the wrong hour?
Cron Triggers run in UTC, not your local time zone.
Is my expression sent anywhere?
No. It is evaluated in your browser.
Test scheduled Workers locally.
WorkerDock runs every project with its own port and logs, so you can hit the cron test route and watch the output without hunting for a terminal tab.