*/5 * * * * is locked to the clock. It is also ruthless about the next fire. On traditional Vixie cron, a job that takes six minutes will overlap itself on that schedule. The daemon starts the command when the minute matches. It does not skip because the previous process is still going.

Build the five fields in the cron expression generator. The page does not install the job. Copy the line into the crontab on the host that will run it.

What overlap looks like

Suppose the command starts at 10:00 and is still running at 10:05. Classic cron starts another instance at 10:05. Two processes share the same work. systemd timers and queue workers can behave differently. This warning is about classic cron.

If the work must not overlap, take a lock inside the command and keep the schedule as it is. flock is a common pattern. Call the program by its absolute path. Cron’s PATH is often shorter than your login shell.

Related mistakes on the same line

*/5 does not mean five minutes after you save the crontab. Install it at 10:03 and the next run is 10:05. There is no seconds field on a five-field line. Quartz puts seconds first. EventBridge uses six fields and ? in a day field. A five-field line matches neither shape.

One cycle on the host

*/5 * * * * date >> /tmp/cron-every-5.log 

Wait for two lines five minutes apart, then remove the test. For real jobs, add the lock before the absolute path of the program.

Guide: https://kepttools.com/guides/cron-every-5-minutes