Every 6 Months Cron Expression — 0 0 1 */6 *
Cron Expression
0 0 1 */6 *What it means
Runs on the 1st of January and July
Good for semi-annual certificate rotation, archiving first-half and second-half business data, or triggering bi-annual security audits.
Next 8 Scheduled Runs (UTC)
- 1.Wed, 01 Jul 2026 00:00:00 GMT
- 2.Fri, 01 Jan 2027 00:00:00 GMT
- 3.Thu, 01 Jul 2027 00:00:00 GMT
- 4.Sat, 01 Jan 2028 00:00:00 GMT
- 5.Sat, 01 Jul 2028 00:00:00 GMT
- 6.Mon, 01 Jan 2029 00:00:00 GMT
- 7.Sun, 01 Jul 2029 00:00:00 GMT
- 8.Tue, 01 Jan 2030 00:00:00 GMT
Platform Snippets
GitHub Actions
- cron: '0 0 1 */6 *'
Kubernetes CronJob
schedule: "0 0 1 */6 *"
AWS EventBridge
cron(0 0 1 */6 ? *)
AWS uses a 6-field format with year and requires either DOM or DOW to be ?.
systemd Timer
[Timer] OnCalendar=*-*-1 00:00:00 Persistent=true
Want to decode a different expression or test your own?
Test this expression interactively →FAQ
What does the cron expression 0 0 1 */6 * mean?
Runs on the 1st of January and July. Good for semi-annual certificate rotation, archiving first-half and second-half business data, or triggering bi-annual security audits.
How do I use 0 0 1 */6 * in GitHub Actions?
Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 0 1 */6 *'. This will run your workflow runs on the 1st of january and july. Note that GitHub Actions uses UTC time.
Is the cron expression 0 0 1 */6 * valid for Kubernetes CronJobs?
Yes. Set the schedule field in your CronJob spec to "0 0 1 */6 *". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.