Weekly Job at 1:15 AM Every Thursday

cron expression Standard
$ 15 1 * * 4

Runs every Thursday at 1:15 AM.

15
Minute
1
Hour
*
Day of Month
*
Month
4
Day of Week

* In a Nutshell

The cron expression 15 1 * * 4 runs Runs every Thursday at 1:15 AM.. This schedule is ideal for routine weekly tasks that don't require immediate attention and can tolerate slight delays. Examples include generating weekly reports, performing non-critical system maintenance, or synchronizing data that is updated daily.

* When to use this

Use 15 1 * * 4 when a recurring task needs to run Runs every Thursday at 1:15 AM.. This schedule is commonly associated with weekly schedules workloads. 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 1 * * 4 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.

Platform Implementations

Bash

Add this line to your crontab using 'crontab -e'.

bash
0 15 1 * * 4

Last verified:

Nodejs

Use a library like 'node-cron' and schedule a task with this expression.

nodejs
0 15 1 * * 4

Last verified:

Python

Utilize libraries like 'APScheduler' or 'schedule' to integrate this cron expression into your Python application.

python
0 15 1 * * 4

Last verified:

Golang

Employ the 'robfig/cron' library in your Go application to schedule jobs based on this cron string.

golang
0 15 1 * * 4

Last verified:

Java

Incorporate a scheduling library like Quartz Scheduler and configure a cron trigger with this expression.

java
0 15 1 * * 4

Last verified:

Kubernetes

Define a CronJob resource in Kubernetes and set the 'schedule' field in the job's template spec to '15 1 * * 4'.

kubernetes
{
  "schedule": "15 1 * * 4"
}

Last verified:

AWS EventBridge Equivalent

Standard cron expressions often need conversion for AWS EventBridge schedules.

EventBridge Rule
cron(15 1 ? * 4 *)

Frequently Asked Questions

What does '15 1 * * 4' mean?

This cron expression means the job will run at minute 15 past hour 1 on every day of the month, every month, but only on day 4 of the week (Thursday).

What timezone does this expression run in?

Cron expressions typically run in the timezone of the server where the cron daemon is running. It's crucial to ensure the server's timezone is set correctly or to use UTC and adjust accordingly if your business logic relies on a specific local time.

How can I verify this cron job is running correctly?

You can verify by checking the cron logs (often located in /var/log/syslog or similar) for entries related to your job. Alternatively, add logging within your script to confirm execution at the scheduled time.

What is a common variant of this expression?

A common variant might be '15 1 * * 5' which would schedule the job for Friday instead of Thursday, or '0 2 * * 4' for 2:00 AM every Thursday.

What is a potential gotcha with this expression?

If your job takes longer than an hour to run, and it starts at 1:15 AM, the next run at 1:15 AM the following Thursday might be impacted or lead to overlapping executions, especially if the job is resource-intensive.

More schedules like this

Explore Weekly Schedules →

* Try any expression

Standard, Quartz, AWS EventBridge, Jenkins, named schedules (@daily, @hourly…)

* Keep Exploring

Related expressions you might need