BackendBench
Coffee

Home › Convert › Spring to Apache Airflow

Spring → Apache Airflow

Convert Spring cron to Apache Airflow

Spring expressions look similar to Apache Airflow, but the differences matter. Paste yours below; the result is checked against the original run times.

Result

    What changes from Spring to Apache Airflow

    Worked examples

    ScheduleSpringApache Airflow
    every minute0 * * * * ** * * * *
    every 5 minutes0 */5 * * * **/5 * * * *
    every 10 minutes0 */10 * * * **/10 * * * *
    every 15 minutes0 */15 * * * **/15 * * * *
    every 30 minutes0 */30 * * * **/30 * * * *
    every hour0 0 * * * *0 * * * *
    every 2 hours0 0 */2 * * *0 */2 * * *
    every 3 hours0 0 */3 * * *0 */3 * * *

    Conversions that come with a warning

    Field layout and time zones

    Spring

    second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    Spring evaluates in the server time zone by default. Add zone = "UTC" (or any ZoneId) to @Scheduled to make it explicit.

    Apache Airflow

    minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.

    Go the other way

    Convert Apache Airflow to Spring, or open the Spring builder or the Apache Airflow builder.

    Frequently asked questions

    How do I convert a Spring cron expression to Apache Airflow?

    Paste it into the converter above with Spring as the source and Apache Airflow as the target. For example, 0 * * * * * becomes * * * * *.

    Is every Spring expression convertible to Apache Airflow?

    Yes for the common schedules we tested (32 of 32), though unusual expressions with special characters might need manual review.

    Does Apache Airflow run in the same time zone as Spring?

    Not necessarily. Conversion changes the syntax, not the time zone. Check where each system evaluates the schedule before you rely on the same clock times.

    More tools you might need