Cron weekdays at 23:00: the expression, explained, in Node.js

The cron expression for “weekdays at 23:00” is 0 23 * * 1-5. This page shows what each field does, the next five times it will fire, the mistake most people make with it, and a working Node.js example you can paste.

The expression

0 23 * * 1-5

Field	Value	Meaning
minute	0	exactly 0
hour	23	exactly 23
day of month	*	every day of month
month	*	every month
day of week	1-5	Monday to Friday

Next five runs (UTC, from now)

2026-09-17 23:00 UTC
2026-09-18 23:00 UTC
2026-09-21 23:00 UTC
2026-09-22 23:00 UTC
2026-09-23 23:00 UTC

Mistakes people make with this schedule

Day-of-week "1-5" is Monday to Friday, but cron knows nothing about public holidays. The job still fires at 23:00 on Christmas Day; skip holidays in the job, not in the expression.
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

Linux crontab Laravel WordPress Next.js / Vercel Node.js Python Docker GitHub Actions

import cron from 'node-cron';

cron.schedule('0 23 * * 1-5', async () => {
  await runReport();
}, { timezone: 'UTC' });

In-process schedulers die with the process. Fine for one long-lived server, not for serverless.

Questions

Does 0 23 * * 1-5 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.