A 5-field POSIX cron expression encodes `minute (0-59) hour (0-23) day-of-month (1-31) month (1-12) day-of-week (0-6)`. Cloud runners including GitHub Actions, Netlify Scheduled Functions, and Kubernetes CronJobs execute strictly in UTC—and POSIX specifies logical OR (not AND) whenever both Day-of-Month and Day-of-Week are restricted away from `*`.
How to Use Cron Time Checker
- 1Enter a 5-Field Cron Expression or Load a Production Preset
Type any `* * * * *` pattern or `@monthly` alias, or choose presets like Every 30 mins, Off-peak Hourly (:13), or Weekdays 09:00 UTC.
- 2Verify Plain-English Semantics & Upcoming 12 UTC Firing Times
Confirm the human translation and scan the next 12 simulated UTC execution timestamps to eliminate timezone offsets or Day-of-Month/Day-of-Week OR surprises.
- 3Copy Cloud Runner Config Into GitHub Actions or Netlify
Copy generated YAML or TOML directly into `.github/workflows/*.yml`, `netlify.toml`, or server crontabs.
Core Capabilities & Specifications
- Supports 5-field syntax plus `@hourly`, `@daily`, `@midnight`, `@weekly`, `@monthly`, `@yearly` macros
- Plain-English schedule translation paired with the next 12 exact UTC execution timestamps
- Accepts both `0` and `7` as Sunday in Day-of-Week schedules
- 1-click presets for AI RSS pipelines, off-peak hourly syncs, and weekday B2B digests
- Generates copy-ready GitHub Actions YAML, `netlify.toml`, and Unix `crontab` config
Understanding 5-Field UTC Cron Execution Semantics & The POSIX OR Quirk
Cloud automation platforms—including GitHub Actions `schedule`, Netlify Scheduled Functions, Cloudflare Cron Triggers, AWS EventBridge (cron mode), and default Kubernetes `CronJob` controllers—evaluate schedules in **UTC** rather than local team timezones. Forgetting UTC offset conversion shifts scheduled email newsletters, RSS ingestion pipelines, and billing rollups by 5–8 hours.
Equally subtle is the POSIX Day-of-Month (`dom`) vs Day-of-Week (`dow`) specification rule: if one of them is `*`, the restricted field controls firing. However, if **both** `dom` and `dow` specify values (for instance `0 9 13 * 5` thinking 'only Friday the 13th'), traditional cron triggers whenever **either** matches—running every Friday PLUS the 13th of every month!
name: AI RSS & IndexNow Scheduled Dispatch
on:
schedule:
# Run at minute 17 past every 4th hour UTC (avoids :00 top-of-hour runner queues)
- cron: '17 */4 * * *'
workflow_dispatch:
jobs:
sync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm run rss:syncAvoiding Top-of-the-Hour Queue Spikes (`:00` Congestion)
Across multi-tenant CI platforms like GitHub Actions and serverless schedulers, hundreds of thousands of repositories configure `0 * * * *` (`@hourly`) or `0 0 * * *` (`@daily`). At `HH:00:00Z`, worker pools experience sharp cold-start queuing delays ranging from 4 to 25 minutes—or dropped runs entirely under heavy load.
Staggering automated crons onto prime off-peak minutes like `13 * * * *` or `23 2 * * *` bypasses thundering-herd queues cleanly and produces far more predictable execution latencies.
Idempotency & Overlap Locking for Long-Running Scheduled Jobs
If a `*/15 * * * *` RSS synthesis or database compaction script takes 18 minutes during a transient API slowdown, the next tick can spawn a concurrent duplicate worker—causing duplicate articles, race-condition billing charges, or lock contention. Wrap scheduled endpoints cleanly with distributed locks (PostgreSQL advisory locks or Redis `SET NX EX`), `concurrencyPolicy: Forbid` on Kubernetes CronJobs, and `workflow_dispatch` idempotency keys.
# netlify.toml
[functions."rss-cron"]
# Triggers every 6 hours at minute 19 UTC
schedule = "19 */6 * * *"Engineering Comparison Matrix
| Macro / Expression | Plain English Meaning | Minimum Cloud Platform Note |
|---|---|---|
| `*/15 * * * *` | Every 15 minutes | Netlify & GitHub Actions support down to 1-min / 5-min cadence |
| `13 * * * *` | Hourly at minute :13 UTC | Strongly preferred over `0 * * * *` to skip runner queues |
| `30 2 * * 1-5` | At 02:30 UTC Monday through Friday | Ideal for weekday B2B digests & database vacuuming |
| `0 0 * * 0` (`@weekly`) | Sunday 00:00 UTC | Both `0` and `7` represent Sunday in POSIX/Linux cron |
| `0 0 1 * *` (`@monthly`) | 00:00 UTC on Day 1 of month | Safe across all 28/29/30/31-day months |
Common Production Pitfalls to Avoid
- •Scheduling production syncs at `:00` minutes on the hour when shared CI runners hit maximum queue lag.
- •Assuming GitHub Actions or Netlify crons fire in local EST/PST/PKT time instead of UTC.
- •Combining non-wildcard `Day-of-Month` and `Day-of-Week` (`15 * 1-7 * 1`) without realizing POSIX evaluates them as logical OR.
- •Triggering expensive AI workflows every 5 minutes without distributed locking against overlapping long runs.
- •Putting 6-field seconds (`* * * * * *`) into standard 5-field POSIX/GitHub/Netlify parsers.
Frequently Asked Questions
Why should I avoid `0 * * * *` for GitHub Actions crons?
Millions of repositories fire at minute `0` on the hour, creating heavy GitHub Actions runner backlog. Selecting an off-peak minute such as `13 * * * *` or `47 * * * *` dramatically improves trigger punctuality.
What timezone do Netlify Scheduled Functions and GitHub Actions use?
Both platforms evaluate all cron expressions exclusively in Coordinated Universal Time (UTC).
What does `dom` AND vs OR `dow` mean in standard cron?
When both Day-of-Month and Day-of-Week are specified (not `*`), POSIX cron runs if EITHER matches (e.g. `0 9 1 * 1` runs on the 1st of the month AND every Monday). Filter inside your application script if you strictly need logical AND (such as 'first Monday').
Are `@daily` and `@weekly` supported everywhere?
Linux Vixie cron and many cloud platforms accept `@hourly`, `@daily`, `@weekly`, `@monthly`, and `@yearly`. However, GitHub Actions and Netlify explicitly require standard 5-field numeric cron syntax (`0 0 * * *`).
Does standard 5-field cron support seconds?
No. Standard POSIX, Linux crontab, GitHub Actions, Netlify, and Kubernetes CronJobs use 5 fields starting at minutes (`0–59`). AWS Quartz (6 fields) and Spring (`@Scheduled`) use separate 6-field dialects.
What happens if I schedule a job on Day 31 (`0 0 31 * *`)?
The job simply skips months with fewer than 31 days (February, April, June, September, November) and fires only in 31-day months.

