What is Predefined Schedule Shortcuts?
Shorthand strings like @daily and @hourly that replace full cron expressions.
Definition
Predefined schedule shortcuts are human-readable alternatives to cron expressions. @yearly (or @annually) equals "0 0 1 1 *", @monthly equals "0 0 1 * *", @weekly equals "0 0 * * 0", @daily (or @midnight) equals "0 0 * * *", @hourly equals "0 * * * *", and @reboot runs once at system startup. Not all cron implementations support all shortcuts.
Simple Analogy
Like speed dial buttons on a phone — instead of typing the full number, you press one button for a preset destination.
Why It Matters
Shortcuts reduce syntax errors and improve readability. "@daily" is instantly understandable by anyone, while "0 0 * * *" requires cron knowledge. CronJobPro supports these shortcuts in its expression input, making schedule creation faster and less error-prone.
How to Verify
Enter a shortcut like @daily in the Cron Explainer to see its full equivalent expression and next run times. Verify it matches your expected schedule.
Common Mistakes
Assuming @daily means "every 24 hours from when I create the job" — it means "at midnight" specifically. Not knowing that @reboot only works with system cron, not SaaS schedulers. Using @monthly and expecting it to run on the 15th — it runs on the 1st.
Best Practices
Use shortcuts for simple, standard schedules where they improve readability. Switch to full expressions when you need customization (specific time, business hours only). Always verify the shortcut expands to what you expect.
Cron Expression Generator
Build your cron expression
Try it free →Frequently Asked Questions
What is Predefined Schedule Shortcuts?
Predefined schedule shortcuts are human-readable alternatives to cron expressions. @yearly (or @annually) equals "0 0 1 1 *", @monthly equals "0 0 1 * *", @weekly equals "0 0 * * 0", @daily (or @midnight) equals "0 0 * * *", @hourly equals "0 * * * *", and @reboot runs once at system startup. Not all cron implementations support all shortcuts.
Why does Predefined Schedule Shortcuts matter for cron jobs?
Shortcuts reduce syntax errors and improve readability. "@daily" is instantly understandable by anyone, while "0 0 * * *" requires cron knowledge. CronJobPro supports these shortcuts in its expression input, making schedule creation faster and less error-prone.
What are best practices for Predefined Schedule Shortcuts?
Use shortcuts for simple, standard schedules where they improve readability. Switch to full expressions when you need customization (specific time, business hours only). Always verify the shortcut expands to what you expect.