Quartz cron — last day of the month

• 0 0 0 L * ? — last day of every month at 00:00.
• 0 0 12 L * ? — last day of every month at 12:00.
• 0 0 0 LW * ? — last weekday of every month at 00:00.
• 0 0 0 L-1 * ? — second-to-last day of every month at 00:00.
• 0 0 12 ? * 6L — last Friday of every month at 12:00 (1=Sunday, 6=Friday in Quartz).
• 0 0 12 ? * 2L — last Monday of every month at 12:00.
• 0 0 0 L 12 ? — last day of December (December 31st) at midnight.

Define the trigger using CronScheduleBuilder:

import org.quartz.*;
import static org.quartz.JobBuilder.*;
import static org.quartz.TriggerBuilder.*;
import static org.quartz.CronScheduleBuilder.*;

JobDetail job = newJob(MonthEndJob.class)
    .withIdentity("monthEndJob", "billing")
    .build();

Trigger trigger = newTrigger()
    .withIdentity("monthEndTrigger", "billing")
    .withSchedule(cronSchedule("0 0 0 L * ?"))
    .build();

scheduler.scheduleJob(job, trigger);

Use cronSchedule for the 6-field syntax with seconds. If you prefer the 7-field form with year, use 0 0 0 L * ? *.

Spring's @Scheduled annotation accepts Quartz-flavoured cron strings (with the same 6-field shape):

@Component
public class MonthEndScheduler {

    @Scheduled(cron = "0 0 0 L * ?", zone = "UTC")
    public void runMonthEndJob() {
        // ...
    }
}

Spring's CronExpression parser is mostly Quartz-compatible but has minor differences (e.g. it supports standard cron ? handling but historically didn't accept L in older versions — Spring 5.3+ does).

• Don't mix `L` with day-of-week values — Quartz throws an exception. Always use ? in the other day field.
• `L` resolves to the calendar last day, not the last business day. Use LW for weekday-aware last day.
• Timezone matters — pass a TimeZone to CronTrigger. Quartz defaults to JVM-local time, which varies by deployment.
• Misfire handling — if the JVM was down at midnight on the last day, Quartz may or may not catch up depending on the misfire instruction. Set it explicitly for month-end jobs.