Skip to content
Docs navigationBrowse tools →

Tool docs

Cron Expression Explainer & Generator

Inspect cron expressions locally, preview upcoming runs, and compare templates without guessing what a schedule means. This guide covers the tool's sweet spot, the scheduler edge cases to watch, and how the preview is computed.

Tool

Overview

01

Cron Expression Explainer & Generator

The Cron tool translates a terse cron string into a readable sentence, previews the next run times in the time zone you choose, and can build an expression from a few choices. It is built for debugging and review, not for pretending that every cron runtime behaves identically.

Guide

Common usage patterns

01

Quick inspection and schedule review

  • Paste a 5-field cron expression or a 6/7-field Quartz one; the tool detects which.
  • Read the plain-language sentence and the per-field cards to confirm each part means what you think.
  • Pick a time zone and inspect the next runs before shipping the schedule into production.
  • No expression yet? Start from a template or choose a frequency in the visual builder.
  • Compare nearby expressions when you are deciding between weekday, weekly, or interval-based schedules.

Guide

Edge cases & common pitfalls

01

DOM/DOW semantics and timezone gotchas

  • Day-of-month and day-of-week matching differs across cron implementations, so a valid expression can still behave differently at runtime.
  • DST and timezone shifts can move real execution times even when the expression itself looks stable.
  • Quartz numbers weekdays 1–7 starting on Sunday while standard cron uses 0–6; copy an expression together with its dialect.
  • A preview is a strong sanity check, but the final authority is still the runtime that will execute the job.

Internals

How it works internally

01

Parser, normalization, and bounded previews

Birdor parses standard 5-field cron (plus common macros) and Quartz 6/7-field expressions, explains them from a structured reading shared with the preview, and computes upcoming runs inside a bounded window. The tool stays explicit about assumptions instead of hiding scheduler ambiguity.