Cron Expression Generator

When to reach for this tool

Reach for this when you need to build a readable cron schedule from plain requirements during setup, debugging, or an incident review. A one-off check is useful for diagnosis, but production systems need continuous monitoring once the immediate question is answered.

• Design the schedule before writing the job, not after.
• Prefer a readable expression over a clever compact one.
• Pair every scheduled job with an owner and a heartbeat.

The five fields of a cron expression

A standard cron expression has five fields, read left to right. Knowing them makes any schedule readable and easy to write correctly the first time.

• Minute (0–59) — which minute of the hour.
• Hour (0–23) — which hour of the day.
• Day of month (1–31) — which date.
• Month (1–12) — which month.
• Day of week (0–6, Sunday=0) — which weekday.

From one-off check to continuous monitor

Use the generator to design the schedule first, then document the job owner and attach a heartbeat that fires after the job completes its work successfully.

• Recreate the same check in Sandglass on an interval so the next change is caught without re-running the lookup.
• Send failures to email, a Slack webhook channel, or a generic webhook owned by whoever fixes the problem.
• Track the result over time instead of treating one manual reading as the final answer.

Why a lookup is not monitoring

A clever expression is worth less than a clear one. Favor a schedule the next engineer can read over a compact string that hides when the job truly runs.