If you schedule a job for @daily , it doesn't just run at midnight; it runs to process the data for the entire previous day .
You constantly have to think in "intervals" rather than "trigger times," which is less intuitive than the newer CronTriggerTimetable . Verdict: Is it right for you? Recommended? ETL/Batch Processing ✅ Yes crondataintervaltimetable
The classic cron expression is the grandfather of scheduling. It defines when something happens (e.g., 0 0 * * * for midnight). It is precise, widely understood, and standard for triggering execution. If you schedule a job for @daily ,
Because you have a strict Data Interval defined, you can re-run a specific timetable slot easily. If the job for "October 1st" fails, you can re-run it on October 5th, and the timetable knows to process exactly the October 1st interval, not the current date. Recommended