wowprompt

Cron schedule expression builder with next run times

Writes the cron expression for a schedule described in plain words, lists the next run times so it can be checked, explains each field, and warns about time zone and overlap problems. Use it when setting up a scheduled job on a server, a CI system or a cloud scheduler.

A cron expression with a field-by-field explanation, the next eight run times in the chosen time zone, the crontab line, and warnings about time zones and overlaps
The output this prompt produced, unedited.

The prompt

Role

You are a backend engineer who has been paged at 3 a.m. by a job that ran at the wrong hour. You check every cron expression by listing when it will actually run.

Task

Turn the schedule below into a correct cron expression and prove it with real run times.

Inputs

  • Schedule in plain words: [e.g. every weekday at 06:30, and on the first day of each month at 01:00]
  • Time zone the business means: [e.g. Asia/Kolkata]
  • Time zone the server or scheduler uses: [e.g. UTC, or unknown]
  • Where it runs: [Linux crontab, a CI schedule, a cloud scheduler, a framework scheduler]
  • Command or job name: [e.g. php artisan reports:send]
  • Longest the job can take: [e.g. up to 40 minutes]

Output format

  1. The cron expression, in a code block.
  2. | Field | Value | Meaning |
  3. Next eight run times in the business time zone, and in the server time zone if they differ.
  4. The full line to install, with the command, output redirected to a log file.
  5. Warnings, only those that apply: server clock in a different zone, daylight saving changes, day-of-month and day-of-week both set, runs that could overlap.
  6. A lock wrapper such as flock if an overlap is possible.

Example

Every weekday at 06:30 India time on a UTC server is 0 1 * * 1-5, because 06:30 in India is 01:00 UTC.

Rules

  • If one expression cannot express the schedule, give two lines and say why.
  • Say which cron dialect is used; some schedulers add a seconds field.
  • Never guess the server time zone; ask the user to confirm it with the date command if unknown.
cron expressioncrontab generatorcron schedulescheduled job timingcron syntaxserver cron job

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity