Comparison
5-Field vs 6-Field Cron: What Changes Between Schedulers
Understand the difference between standard 5-field cron and 6-field variants with seconds so schedules do not silently shift between environments.
Published
Updated
Quick answer
- Standard Unix cron uses 5 fields.
- Some schedulers add a sixth field for seconds.
- A valid expression in one system can be invalid or misread in another.
Why field count matters first
Before you interpret the meaning of the schedule, confirm how many fields the scheduler expects. If one system reads the first field as minutes and another reads it as seconds, the entire expression shifts.
Where teams get caught
This mismatch shows up when moving jobs between Quartz-style runtimes, CI systems, cloud schedulers, and standard cron environments. The schedule may look almost correct while actually running at the wrong cadence.
Safe workflow
Use the Cron Expression Parser to confirm the field breakdown, then use the Timestamp Converter if you need to sanity-check expected run times in UTC or local time.
Keep Reading In This Topic
Adjacent guides that support the same workflow or query family.