tarsolutiontools

Build a schedule and inspect its next execution times.

01 Input

Processed on demand. Never saved.

02 Output

⌘

A little clarity awaits.

Start with a sample or add your own input.
Your result will appear here.

Ready when you areJSON API · no cache
A CLOSER LOOK

The details behind
the result.

Understand the format, the calculation, and what to look for.

Schedule

Compute occurrences without creating a job. Unix uses minute/hour/day/month/weekday; matching day-of-month OR weekday follows croniter semantics.

Special expressions

@hourly, @daily, @weekly, @monthly and @yearly are accepted. @reboot describes an event and has no predictable next date.

Limits

Search is bounded to five years. DST behavior depends on the deployment scheduler: review offset changes before copying. This profile is not Quartz.

Inputs explained

Mode
Mode
Cron expression
Unix five-field cron; Jenkins H requires a hash key. Quartz-specific W syntax is not supported.
Minute
Use *, a list, range or step. Values are validated by croniter.
Hour
Use *, a list, range or step. Values are validated by croniter.
Day Of Month
Use *, a list, range or step. Values are validated by croniter.
Month
Use *, a list, range or step. Values are validated by croniter.
Day Of Week
Use *, a list, range or step. Values are validated by croniter.
Engine profile
Engine profile
Jenkins hash key
Stable job name used for H expressions.
Time zone
IANA zone. Detected from your browser.
Start time
ISO 8601 timestamp with UTC offset. No jobs are scheduled.
Next runs
Next runs