A Quartz job that does not fire is usually waiting for a free worker thread, skipped by its misfire instruction, running on an old schedule kept in the database, or attached to a trigger in the ERROR state; sometimes the scheduler never started. Quartz knows which: the trigger’s state and its next fire time tell you. Here is how to read them, fix each cause, and be alerted the next time a job goes quiet.
Why is my Quartz job not firing?
Quartz does not run a job; it fires a trigger , and the trigger runs the job. When a job goes quiet, the trigger is where the answer is. Five causes cover most cases.
1. The scheduler never started
In Spring Boot, the scheduler starts with the application unless spring.quartz.auto-startup is false . Outside Spring, nothing fires until something calls scheduler.start() .
To confirm, look for Quartz’s own line at startup, Scheduler quartzScheduler_$_NON_CLUSTERED started. with Spring Boot’s default name. If it is not in the log, no trigger will fire.
2.…