Setting Cron Job Runs on Monday of Every Third Thursday

Understanding Cron Limitations

Cron jobs are powerful tools for automation in Unix-like systems, but they operate on fixed fields: minute, hour, day of month, month, and day of week. While you can specify 0 9 * * 4 to run a command at 9 AM every Thursday, this will trigger seven times a month. There is no native cron field that accepts expressions like "the third occurrence" of a weekday. Attempting to solve this with pure cron arithmetic (using modulo operators) is error-prone and difficult to maintain. Therefore, the industry standard solution is to delegate the date logic to a simple shell script.

Creating the Detection Script

The core of this solution is a bash script that determines if the current day meets two criteria: it is a Thursday, and it is between the 15th and 21st of the month. You can create this script in your home directory or a dedicated bin folder. Create a file named third_thursday_job.sh using your preferred text editor.

#!/bin/bash

# Get the current day of the week (0=Sun, 1=Mon, ..., 4=Thu)
DAY_OF_WEEK=$(date +%u)

# Get the current day of the month
DAY_OF_MONTH=$(date +%d)

# Check if it is Thursday (4) and between the 15th and 21st
if [ "$DAY_OF_WEEK" -eq 4 ] && [ "$DAY_OF_MONTH" -ge 15 ] && [ "$DAY_OF_MONTH" -le 21 ]; then
    # Replace this line with your actual command
    echo "Running third Thursday job at $(date)" >> /var/log/third_thursday.log
    
    # Example: /usr/bin/your_command_here
fi

This script uses the date command with format codes %u for the numeric day of the week (where Monday is 1 and Thursday is 4) and %d for the day of the month. The conditional statement ensures that even if the cron daemon triggers the script every day, the actual work only happens when both conditions are true. If the day is not a Thursday, or if it is the first, second, fourth, or fifth Thursday, the script exits silently.

Scheduling the Wrapper

Once the script is created, you need to make it executable and add it to your crontab. First, ensure the script has execution permissions by running chmod +x ~/third_thursday_job.sh. Next, edit your user's crontab by typing crontab -e.

Add the following line to run the script every day at 9:00 AM:

0 9 * * * /home/your_username/third_thursday_job.sh

By scheduling the script to run daily, you cover all days of the week. The logic inside the script handles the filtering. This method is significantly more reliable than trying to manipulate the day-of-month field directly, as it avoids issues with months that have varying numbers of days or leap years. For related scheduling challenges, such as running jobs on specific weekdays like Monday and Thursday, you might find our guide on Setting Cron Job Runs on Monday of Week 3 and Thursday helpful for understanding broader scheduling patterns.

Handling Time Zones and Paths

When working with cron jobs, environment variables are often limited compared to an interactive shell session. It is critical to use absolute paths for both the interpreter (/bin/bash) and any commands executed within the script. If your job relies on external services or scripts located in non-standard directories, always provide the full path. Additionally, be aware that the system's local time zone applies to the date command unless overridden. If your server is set to UTC but you want the job to run based on local business hours, you may need to adjust the TZ environment variable within the script or export it in the crontab header.

Testing and Verification

Before relying on this setup in production, test the logic manually. Run the script directly from the command line: ~/third_thursday_job.sh. Check the log file specified in the script to see if it recorded the execution. To verify the date logic without waiting for the actual day, you can temporarily modify the DAY_OF_MONTH variable in the script to match today's date and run it again. Once verified, remove the test modifications and let the cron daemon handle the timing. For users concerned about privilege escalation during these automated tasks, reviewing best practices for running programs with elevated privileges can prevent security pitfalls, as detailed in our article on Run Programs with Elevated Privileges: A Comprehensive Guide.

Frequently Asked Questions

Can I do this with pure cron syntax?

No, standard cron does not support relative date calculations like "third Thursday." You must use a script wrapper to evaluate the date dynamically. Any attempt to use modulo arithmetic in cron fields will likely result in incorrect execution frequencies.

What if my server timezone is different from my local time?

The date command respects the system's configured timezone. If your server is in UTC but you need Eastern Time, set the TZ variable in your crontab or script before calling date, ensuring the job runs at the intended local hour.

How do I debug why my script isn't running?

Check the system mail logs or the cron log file (often /var/log/syslog or /var/log/cron). Ensure the script has executable permissions and uses absolute paths for all binaries. Redirect stderr to a log file in the crontab line to capture errors.

Can I run this job weekly instead of monthly?

If you want the third Thursday of every week, you would need a different logic check. However, the concept remains the same: use a daily cron trigger and filter by week number or consecutive day counts within the script, as cron cannot natively distinguish between "week 3" globally.

Is there a risk of the job running twice?

If the script takes longer than one minute, it could theoretically overlap with the next cron tick if not managed. Use a lock file mechanism or flock to ensure only one instance runs at a time, preventing duplicate executions during long-running tasks.