Cron every 12 hours at :15: the expression, explained, in Laravel

The cron expression for “every 12 hours at :15” is 15 */12 * * *. This page shows what each field does, the next five times it will fire, the mistake most people make with it, and a working Laravel example you can paste.

The expression

15 */12 * * *
FieldValueMeaning
minute15exactly 15
hour*/12every 12 hours, starting at 0
day of month*every day of month
month*every month
day of week*every day of week

Next five runs (UTC, from now)

  1. 2026-09-18 00:15 UTC
  2. 2026-09-18 12:15 UTC
  3. 2026-09-19 00:15 UTC
  4. 2026-09-19 12:15 UTC
  5. 2026-09-20 00:15 UTC

Mistakes people make with this schedule

  • Using "* */12 * * *" for every 12 hours. That runs every minute of every 12th hour. The minute field must be the fixed number 15.
  • Assuming the server clock is your clock. Cron runs in the machine’s timezone unless the runtime says otherwise; the examples here are UTC.
  • No lock around a job that might overlap itself, and no alert when it silently stops. That second one is what Supercrontab is for.

Run it in your stack

// routes/console.php
Schedule::command('reports:send')
    ->cron('15 */12 * * *')
    ->timezone('UTC')
    ->withoutOverlapping();

Requires the scheduler itself to be started every minute: `* * * * * php artisan schedule:run`.

Questions

Does 15 */12 * * * run in my local time?

Only if the scheduler is configured for it. crontab uses the system timezone; Vercel and GitHub Actions always use UTC; Laravel and node-cron take a timezone option. In Supercrontab the timezone is a field on the job.

What if the previous run is still going?

Classic cron starts the next run anyway. Add a lock (flock on Linux, withoutOverlapping() in Laravel) or let Supercrontab skip the tick while the previous request is open.

Is there a shorter way to write this?

No. The five-field form is the shortest portable version.