Run a Job Every Sunday at 3:30 PM | CronBase
30 15 * * 7 Every Sunday afternoon at 3:30 PM
* In a Nutshell
The cron expression 30 15 * * 7 runs Every Sunday afternoon at 3:30 PM. Weekly schedules are crucial for batch processing tasks that don't require sub-daily frequency. This includes generating weekly reports, performing system maintenance, or initiating data backups that can tolerate a 7-day window, preventing resource contention during peak business hours.
* When to use this
Use 30 15 * * 7 when a recurring task needs to run Every Sunday afternoon at 3:30 PM. This schedule is commonly associated with maintenance window and report generation and weekend 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 30 15 * * 7 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
Prerequisites
Unix/Linux host with a cron daemon running (vixie-cron, cronie, or systemd-cron). The script at /usr/local/bin/run-task.sh must exist and be executable (chmod +x).
Configuration
Run crontab -e to open the crontab editor. Cron reads the server's local timezone; prefix with CRON_TZ=UTC before the expression to pin to UTC. Always redirect output with >> /var/log/cron-tasks.log 2>&1 to capture both stdout and stderr.
Gotchas
Cron jobs inherit a minimal PATH — use full binary paths or set PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin at the top of the crontab. For sub-hourly schedules, add flock -n /tmp/run-task.lock before the command to skip overlapping runs if the previous execution is still running.
# Add to crontab with: crontab -e
30 15 * * 7 /usr/local/bin/run-task.sh >> /var/log/cron-tasks.log 2>&1Last verified:
Nodejs
Prerequisites
Node.js 18+ with node-cron installed (npm install node-cron). Add "type": "module" to package.json to use the import syntax shown above.
Configuration
Pass { timezone: 'UTC' } as the third argument to cron.schedule(). Without this option the schedule uses the Node.js process timezone, which shifts during DST transitions when servers are not pinned to UTC.
Gotchas
node-cron uses standard 5-field cron syntax — not Quartz 6-field. If your job runs longer than the schedule interval the next trigger fires while the previous is still executing. Use a boolean guard or a queue to skip concurrent runs rather than relying on the scheduler to enforce it.
import cron from 'node-cron';
cron.schedule('30 15 * * 7', async () => {
console.log('[cron] running at', new Date().toISOString());
// your task logic here
}, { timezone: 'UTC' });Last verified:
Python
Prerequisites
Python 3.8+ with apscheduler installed (pip install apscheduler). For Python 3.12+ use apscheduler>=3.10.
Configuration
CronTrigger.from_crontab() accepts a standard 5-field cron string. Always pass timezone='UTC' to both the BlockingScheduler constructor and the trigger to ensure consistent scheduling regardless of the server's locale.
Gotchas
BlockingScheduler.start() blocks the calling thread indefinitely. For a web application, use BackgroundScheduler instead and call scheduler.start() at application startup. APScheduler logs missed fires if the process is stopped and restarted — configure misfire_grace_time (in seconds) to control how late a missed job is allowed to run.
from apscheduler.schedulers.blocking import BlockingScheduler
from apscheduler.triggers.cron import CronTrigger
scheduler = BlockingScheduler(timezone='UTC')
@scheduler.scheduled_job(
CronTrigger.from_crontab('30 15 * * 7', timezone='UTC')
)
def run_task() -> None:
print('task running')
# your task logic here
scheduler.start()Last verified:
Golang
Prerequisites
Go 1.18+ and github.com/robfig/cron/v3 (go get github.com/robfig/cron/v3).
Configuration
Always create the scheduler with cron.New(cron.WithLocation(time.UTC)). Without WithLocation, the library defaults to the server's local timezone. Call c.Start() to begin the scheduler, then block with select {} to keep the process alive.
Gotchas
robfig/cron v3 uses standard 5-field cron expressions by default. To add second-level precision (6 fields), pass cron.WithSeconds() to cron.New() — but this changes field positions, so never mix syntaxes in the same scheduler. Always check the error returned by c.AddFunc() — a malformed expression is silently ignored without it.
package main
import (
"fmt"
"time"
"github.com/robfig/cron/v3"
)
func main() {
c := cron.New(cron.WithLocation(time.UTC))
_, err := c.AddFunc("30 15 * * 7", func() {
fmt.Println("task running at", time.Now().UTC())
// your task logic here
})
if err != nil {
panic(err)
}
c.Start()
defer c.Stop()
select {}
}Last verified:
Java
Prerequisites
Spring Boot 2.7+ (or Spring Framework 5.3+) with spring-context on the classpath. Annotate your @SpringBootApplication class with @EnableScheduling — without it, @Scheduled methods are silently ignored.
Configuration
Spring @Scheduled uses a 6-field Quartz-style expression: [sec] [min] [hr] [dom] [mon] [dow]. The expression 0 30 15 ? * 7 is derived from 30 15 * * 7 — a leading 0 is prepended for the seconds field, and ? replaces the unconstrained day field.
Gotchas
Standard Unix cron has 5 fields; Spring requires 6. Pasting a 5-field expression directly into @Scheduled shifts every field by one and the job misfires silently. Use ? for either dom or dow — Quartz does not allow both to be *.
import org.springframework.scheduling.annotation.Scheduled;
import org.springframework.stereotype.Component;
@Component
public class ScheduledTask {
@Scheduled(cron = "0 30 15 ? * 7")
public void runTask() {
System.out.println("task running at: " + java.time.Instant.now());
// your task logic here
}
}Last verified:
Kubernetes
Prerequisites
Kubernetes 1.21+ (CronJob API is GA). kubectl configured with cluster access. Container image must be pullable from within the cluster.
Configuration
Apply with kubectl apply -f cronjob.yaml. Check status with kubectl get cronjobs and inspect run history with kubectl get jobs. concurrencyPolicy: Allow is set because this schedule fires infrequently — parallel runs are acceptable.
Gotchas
Without startingDeadlineSeconds, a missed job (e.g., due to cluster downtime) triggers as soon as the controller recovers. Kubernetes 1.25+ supports timeZone: UTC in the spec to avoid timezone ambiguity. Keep successfulJobsHistoryLimit and failedJobsHistoryLimit low to avoid accumulating stale Job objects in the cluster.
apiVersion: batch/v1
kind: CronJob
metadata:
name: scheduled-task
spec:
schedule: "30 15 * * 7"
concurrencyPolicy: Allow
jobTemplate:
spec:
template:
spec:
restartPolicy: OnFailure
containers:
- name: task
image: alpine:3.19
command: ["/bin/sh", "-c", "echo 'task running'"]Last verified:
AWS EventBridge Equivalent
Standard cron expressions often need conversion for AWS EventBridge schedules.
cron(30 15 ? * 7 *)Frequently Asked Questions
What does the `30 15 * * 7` cron expression specifically do?
This cron expression is configured to trigger an action exactly once per week, specifically on Sunday at 3:30 PM. It's a precise schedule for tasks that need to occur at the same time each week.
How does this schedule handle time zone changes and daylight saving time?
Cron jobs run based on the server's system clock. Any adjustments for time zones or daylight saving shifts will affect the exact time the job executes, potentially shifting it by an hour during DST transitions.
How can I verify that my job is running correctly with this schedule?
You can verify the job's execution by checking the logs generated by the task itself. Look for entries corresponding to the scheduled run time, confirming both the start and successful completion.
What potential issues or gotchas should I be aware of with this schedule?
A key consideration is ensuring the task completes before the next scheduled run. If the task takes longer than a week, or if the system is down precisely at 3:30 PM on a Sunday, the run could be missed without specific retry mechanisms.
Are there common variations or alternative schedules to this one?
A frequent alternative is to adjust the day of the week for more flexibility. For example, scheduling for Saturday instead of Sunday or shifting the time slightly earlier or later might better suit operational needs.
More schedules like this
Explore Maintenance Window →* Try any expression
Standard, Quartz, AWS EventBridge, Jenkins, named schedules (@daily, @hourly…)
* Keep Exploring