CronCraft

CronCraft

About CronCraft

A small studio for a small syntax that causes a surprising number of production incidents.

This page is written in English. The studio is available in 한국어, 日本語 and 繁體中文.

CronCraft is a browser based workbench for cron expressions. It reads an expression, explains it in plain language, resolves the next executions in a real time zone, scans for daylight saving problems, finds jobs that collide and writes the same schedule for four platforms. It exists because the gap between "the expression is valid" and "the schedule is correct" is where most cron incidents live.

Who it is for

Backend and platform engineers, SREs and DevOps teams who edit crontabs and workflow files, and anyone who has copied a five field expression into a system with six fields. It is also useful for reviewing someone else's schedule: paste the line, read the next runs, and see whether the intent matches.

How the engine works

The parser, the timezone resolution and the next run search are written in plain JavaScript. Time zone offsets come from the browser's implementation of the IANA database through Intl.DateTimeFormat. The next run search walks civil time and resolves each candidate back to a UTC instant, which makes the spring forward gap and the fall back overlap visible instead of silently wrong. The collision checker walks every minute in the selected window and counts matches. The exporters translate the parsed fields; they do not pattern match the original string.

The engine is tested against an independent Python implementation using zoneinfo across dozens of expressions and eight time zones, including both daylight saving transitions and zones with 30 and 45 minute offsets.

What it does not do

It does not connect to your servers, read your crontab automatically, or deploy anything. It does not store expressions, because storing them would mean keeping data about your infrastructure. It does not claim to model every vendor specific extension. When a rule has no direct equivalent in an export format, the generated file says so instead of guessing.

Contact

Questions, corrections and bug reports: [email protected].