Run Every Wednesday at 10:00 AM | CronBase

cron expression Standard
$ 0 10 * * 3

Every Wednesday morning at ten o'clock.

The `0 10 * * 3` cron expression schedules a job to execute automatically every Wednesday at exactly 10:00 AM. This mid-week, mid-morning slot is highly effective for running operational reports, triggering weekly team sync pipelines, or performing maintenance tasks that require active developer supervision during regular business hours.

Minute
0
Hour
10
Day of Month
*
Month
*
Day of Week
3
How it works

Next 5 Runs

  • in 3d 13h
  • in 10d 13h
  • in 17d 13h
  • in 24d 13h
  • in 31d 13h

* Tools

Code & Implementations

Bash
#!/usr/bin/env bash
# To install this system-wide, add the following line to your crontab:
# 0 10 * * 3 /usr/local/bin/wednesday-cleanup.sh

set -euo pipefail

LOG_FILE="/var/log/wednesday_cleanup.log"
exec 3>&1 1>>"${LOG_FILE}" 2>&1

echo "[$(date -u +'%Y-%m-%dT%H:%M:%SZ')] Wednesday morning cleanup job started."

# Perform a safe, non-blocking cleanup of temporary files
find /tmp/app-cache -type f -mtime +7 -delete || {
    echo "[$(date -u +'%Y-%m-%dT%H:%M:%SZ')] Error: Cleanup failed." >&3
    exit 1
}

echo "[$(date -u +'%Y-%m-%dT%H:%M:%SZ')] Wednesday cleanup completed successfully."
Setup notes

Save this script to /usr/local/bin/wednesday-cleanup.sh, make it executable with chmod +x, and register it in your crontab using 'crontab -e'.

Last verified:

Partner BetterStack

Monitor this schedule in production

Get alerted the moment this cron job fails, is late, or doesn't run. BetterStack tracks execution, duration, and output — no infrastructure required.

Platform Equivalents

AWS EventBridge

Standard cron expressions often need conversion for AWS EventBridge schedules.

EventBridge Rule
cron(0 10 ? * 3 *)

Systemd Timer

OnCalendarWed *-*-* 10:00:00

my-task.timer
[Unit]
Description=Timer for cron expression: 0 10 * * 3

[Timer]
OnCalendar=Wed *-*-* 10:00:00
Persistent=true

[Install]
WantedBy=timers.target

Last verified:

Frequently Asked Questions

How does daylight saving time affect this Wednesday 10:00 AM schedule?

If your system timezone is set to a region observing Daylight Saving Time (DST), the execution time will shift relative to UTC but remain at 10:00 AM local time. To avoid shifting execution windows in global environments, configure your system or scheduler to run on UTC.

Can I run this job on both Wednesday and Thursday at 10:00 AM?

Yes, you can modify the day-of-week field to include both days. Changing the expression to `0 10 * * 3,4` will trigger the execution at 10:00 AM on both Wednesdays and Thursdays.

What happens if the server is offline on Wednesday at 10:00 AM?

Standard system cron will skip the execution entirely. If you require the job to run immediately upon system recovery, you should use a tool like `anacron` or configure a catch-up policy in your container orchestrator.

Is 10:00 AM Wednesday safe for high-volume database maintenance?

Generally, no. 10:00 AM is typically a peak usage hour for business applications. Running heavy database queries or vacuum operations during this time can cause lock contention and latency spikes. Move heavy maintenance tasks to off-peak weekend hours instead.

How can I test this Wednesday cron schedule locally without waiting?

You can test the execution logic by temporarily changing the cron expression to run every minute (`* * * * *`) in a staging environment, or manually triggering the underlying script or Kubernetes Job out-of-band to verify its behavior.

* Explore

Related expressions you might need

Last verified:

Was this helpful?