A user crontab runs as its owner while a system table names a separate execution account.

Cron system and user tables have different contracts

Cron accepts schedules from more than one kind of table. A user crontab belongs to one account, while system tables can name the account for each entry. Copying a line between them without adjusting its fields changes what cron interprets as the command. Identify the table format before debugging an apparently correct five-field calendar expression. ...

January 12, 2028 · 5 min · XB Field Notes
A second calendar trigger overlaps ordinary work but records a skip when a lock is held.

Cron repeats on the calendar

Cron matches calendar fields and launches commands at matching times. It does not inherently wait for an earlier invocation of the same command to finish. If a minute-level task takes seventy seconds, the next minute can launch another copy. Treat trigger policy, concurrency policy, and successful completion as separate responsibilities when operating recurring work. ...

September 30, 2027 · 5 min · XB Field Notes