BBoltlyze

Cron Expression Explainer

Interpret a standard five-field cron expression, a seconds-based variant or Quartz format with field-by-field explanations. Verify schedules in the target scheduler.

0/200

How to use it

  1. 1

    Paste the expression

    Copy an expression from your scheduler, without surrounding configuration. The input limit is 200 characters; accepted symbols depend on the selected format.

  2. 2

    Choose the format

    Choose five-field standard for classic crontab, seconds-prefixed six-field for compatible schedulers, or Quartz for its seconds field and optional year. AWS EventBridge uses a different six-field format without seconds; it has no dedicated option here.

  3. 3

    Read it field by field

    Each row pairs a raw field with a proposed meaning; the last row summarizes the schedule. Check the explanation in the target scheduler before using it.

  4. 4

    Watch for the traps

    Some standard cron implementations use OR when both day fields are restricted. Quartz does not support specifying both day fields: use ? in one and verify the result in your scheduler.

0 30 2 ? * MON-FRI is either a schedule or a typo — and until you can read cron fluently, you can't tell which. Cron is compact, everywhere, and almost nobody writes it often enough to stay sharp at it. It lives in crontabs, Kubernetes CronJobs, Quartz configs, and CI pipelines, usually written once by one person and decoded months later by someone else. This tool is the decoder.

Paste the expression and pick the format. The five-field standard is minute, hour, day-of-month, month and day-of-week. The seconds-prefixed option adds seconds at the front. Quartz also has a leading seconds field and an optional trailing year, along with field-specific special characters such as ?, L, W and #. The selector tells the model which field order to interpret.

The requested output is a field-by-field table and a short schedule summary. Treat it as an explanation draft: check field order, time zone, day-of-month/day-of-week behavior and special characters in the target scheduler's documentation or test environment before deploying a schedule.

Day-field rules differ. Some classic cron implementations use OR when both day-of-month and day-of-week are restricted. Quartz does not fully support specifying both fields and requires ? in one of them; do not assume an AND rule. For example, 0 30 2 ? * MON-FRI is a Quartz expression for 02:30 on weekdays in the configured scheduler time zone. Check the Quartz CronTrigger documentation and your scheduler's configuration, including daylight-saving behavior.

Not every six-field expression starts with seconds. For example, Amazon EventBridge scheduled rules use minute, hour, day-of-month, month, day-of-week and year, with no seconds field. This tool has no dedicated EventBridge mode; do not select seconds-prefixed or Quartz merely because the expression has six fields. Check the target scheduler's own validator and time zone.

Input is capped at 200 characters. The expression is sent through Boltlyze's gateway to its AI model provider; the usage-event database excludes the raw prompt, and provider handling follows its own terms. See the Privacy Policy and avoid submitting secrets.

FAQ

What cron formats does this support?

The model is asked to explain classic five-field crontab, a seconds-prefixed six-field variant, or Quartz with an optional trailing year. Syntax varies across implementations. EventBridge has a different field order and no dedicated mode here; check its documentation rather than treating it as seconds-prefixed.

Can it explain Quartz characters like L, W, and #?

The prompt asks for L, W, # and ? to be explained in Quartz context. The model can make mistakes, and each character is valid only in particular fields; check the explanation with the Quartz documentation.

Does it convert expressions between formats?

No — it reads one expression and explains it. Moving a five-field crontab to Quartz usually means adding a 0 for seconds and resolving the ? placeholders by hand, which is exactly the kind of detail worth checking yourself.

Does it account for time zones?

The expression alone may not specify the time zone. Check the scheduler and job configuration: the environment or scheduler can set it separately, and daylight-saving changes can skip or repeat scheduled times.

What happens if the expression is invalid?

For six- or seven-field Quartz expressions, the gateway rejects an expression when both day-of-month and day-of-week are specified. Other mistakes are left to the model, which is not a deterministic validator. Confirm field counts, ranges and special characters with your scheduler before relying on a result.

Related tools