Run Job Every Tuesday at 11:15 AM | CronBase
15 11 * * 2 Every Tuesday at quarter past eleven in the morning
* In a Nutshell
The cron expression 15 11 * * 2 runs Every Tuesday at quarter past eleven in the morning. This schedule is ideal for tasks that need to run consistently on a specific day of the week, like weekly status reports or system maintenance. Running at a predictable time like 11:15 AM ensures these critical operations don't interfere with peak business hours, maintaining system stability and data integrity.
* When to use this
Use 15 11 * * 2 when a recurring task needs to run Every Tuesday at quarter past eleven in the morning. It uses Standard (5-Field POSIX) syntax, supported by Unix cron daemons, cloud schedulers such as AWS EventBridge, and container orchestration platforms such as Kubernetes CronJob.
CronBase parses 15 11 * * 2 using a dialect-aware rules engine that identifies the Standard (5-Field POSIX) format, validates field structure against the Standard (5-Field POSIX) specification, and produces the translation above. Next run times are calculated by forward-scanning from the current UTC clock. Learn how CronBase works.
AWS EventBridge Equivalent
Standard cron expressions often need conversion for AWS EventBridge schedules.
cron(15 11 ? * 2 *)Frequently Asked Questions
What specific action does the `15 11 * * 2` cron expression trigger?
This expression is configured to trigger an action precisely at 11:15 AM every Tuesday. It's a fixed weekly schedule.
How does this schedule handle Daylight Saving Time clock changes?
Cron schedulers typically adjust automatically for Daylight Saving Time. However, always verify your specific system's behavior during clock shifts to prevent unexpected downtime or missed jobs.
How can I verify that the scheduled task is running correctly?
You can confirm the task's execution by checking system logs for entries timestamped at 11:15 AM on Tuesdays. Monitoring tools or application-specific logs will also indicate successful runs.
What potential issues might arise with this specific Tuesday schedule?
A key consideration is ensuring the task completes before the next scheduled run. If the task takes longer than a week, or if clock changes occur, it could lead to overlapping executions or missed jobs.
Are there common variations of this Tuesday timing?
A frequent alternative is to run the task earlier or later in the day, such as at 9 AM or 5 PM on Tuesdays. You could also adjust the day, for instance, scheduling for Mondays instead.
Related Concepts
* Try any expression
Standard, Quartz, AWS EventBridge, Jenkins, named schedules (@daily, @hourly…)