Read and Translate Spring Boot @Scheduled Cron Expressions

Spring Boot's @Scheduled annotation uses a 6-field cron format that adds seconds as the first field — not the 5-field standard that most cron translators expect. Paste the 5-field portion (drop the leading seconds value) into our free crontab visualizer for an instant English translation and next run times.

This guide explains how to read any Spring @Scheduled expression, including the timezone attribute, macro shortcuts, and the fixedDelay vs cron difference.

Spring Boot 6-Field Format vs Standard 5-Field Cron

Standard cron has 5 fields: minute hour day month weekday. Spring Boot adds a seconds field at the beginning, making it 6 fields: seconds minute hour day month weekday.

// Standard cron — runs every day at 9:00 AM
0 9 * * *

// Spring Boot @Scheduled — same schedule
@Scheduled(cron = "0 0 9 * * *")
//                  ^ seconds field added

To translate a Spring expression using the visualizer:

1. Remove the first field (seconds).
2. Paste the remaining 5 fields into the crontab visualizer.
3. The translation and next run times will be accurate for the hour/minute/day part (seconds precision is lost but usually irrelevant for scheduling purposes).

Example: Spring expression 0 30 9 * * MON-FRI → drop the leading 0 → 30 9 * * MON-FRI → translates to "At 9:30 AM, Monday through Friday."

Common Spring @Scheduled Patterns Translated to English

Spring Expression	5-Field Equivalent	English
0 * * * * *	* * * * *	Every minute
0 0 * * * *	0 * * * *	Every hour at :00
0 0 9 * * *	0 9 * * *	Every day at 9:00 AM
0 0 0 * * *	0 0 * * *	Every day at midnight
0 30 9 * * MON-FRI	30 9 * * 1-5	9:30 AM, Mon-Fri
0 0 0 1 * *	0 0 1 * *	1st of each month at midnight
0 0 2 * * SUN	0 2 * * 0	Every Sunday at 2:00 AM
0 */15 * * * *	*/15 * * * *	Every 15 minutes
0 0 9-17 * * MON-FRI	0 9-17 * * 1-5	Hourly 9 AM-5 PM, Mon-Fri

Spring day-of-week names: Spring accepts both numeric (0-7) and three-letter names (MON, TUE, WED, THU, FRI, SAT, SUN). Use names when sharing expressions with team members — they're clearer than numbers.

Sell Custom Apparel — We Handle Printing & Free Shipping

Using the zone= Attribute for Timezone Control

Spring's @Scheduled accepts a zone attribute to run in a specific timezone:

@Scheduled(cron = "0 0 9 * * MON-FRI", zone = "America/New_York")
public void morningTask() {
    // Runs at 9 AM New York time, DST-aware
}

Without zone, Spring uses the JVM's default timezone (set with -Duser.timezone=... or TimeZone.setDefault(...)). In Docker/Kubernetes deployments, the JVM timezone defaults to UTC unless you explicitly configure it.

IANA timezone names (e.g., America/Chicago, Europe/London) are recommended over abbreviations (CST, BST) because abbreviations can be ambiguous.

To verify the schedule in the visualizer, paste the 5-field version and remember that the visualizer uses your browser's local timezone — adjust mentally for the zone attribute value.

@Scheduled: cron vs fixedDelay vs fixedRate

Spring offers three scheduling approaches — they behave differently:

Attribute	Behavior	Best for
cron	Fires at specific wall-clock times defined by the cron expression	Time-based scheduling (daily at 9 AM, every Friday)
fixedDelay	Waits N ms after the previous execution finishes, then runs again	Tasks where you want a gap between runs, regardless of execution time
fixedRate	Runs every N ms from startup, regardless of how long the task takes	Polling tasks where you need consistent intervals from start time

For calendar-based timing (run at midnight, run on weekdays), always use cron. For backoff-style polling (check every 5 seconds after the last check completes), use fixedDelay.

You can also externalize the cron expression to application.properties:

# application.properties
app.schedule.morning=0 0 9 * * MON-FRI

// Java
@Scheduled(cron = "${app.schedule.morning}")
public void morningJob() { ... }

Frequently Asked Questions

Why does my Spring @Scheduled cron have 6 fields instead of 5?

Spring Boot adds a seconds field as the first position, making it a 6-field format: "seconds minute hour day month weekday." Standard Unix cron only has 5 fields. When using our visualizer (which uses 5-field standard cron), drop the first field (seconds) before pasting.

What does "0 0/5 * * * ?" mean in Spring?

This is a Spring/Quartz-style expression: 0 seconds, every 5 minutes (0/5 means starting at 0, then every 5), every hour, every day, every month. The "?" is a Quartz wildcard for "no specific value" in the day-of-week or day-of-month field. The 5-field equivalent is "*/5 * * * *" — every 5 minutes.

How do I make Spring @Scheduled work across Daylight Saving Time?

Use the zone= attribute with an IANA timezone name (e.g., zone = "America/New_York") instead of relying on the JVM default. Spring will handle DST transitions automatically when a proper IANA timezone is specified. Avoid using UTC offset strings like "+05:30" as they don't observe DST.