Cron expression explainer / Every 3 hours
Cron expression for every 3 hours: 0 */3 * * *
Runs at 00:00, 03:00, 06:00 and so on, 8 times a day.
Every 3 hours, on the hour.
- Thu, Nov 19, 2026, 03:00
- Thu, Nov 19, 2026, 06:00
- Thu, Nov 19, 2026, 09:00
- Thu, Nov 19, 2026, 12:00
- Thu, Nov 19, 2026, 15:00
- Thu, Nov 19, 2026, 18:00
- Thu, Nov 19, 2026, 21:00
- Fri, Nov 20, 2026, 00:00
- Fri, Nov 20, 2026, 03:00
- Fri, Nov 20, 2026, 06:00
Field by field
- 0minute
- */3hour
- *day of month: any value
- *month: any value
- *day of week: any value
Variations
- 30 */3 * * *Every 3 hours at half past (00:30, 03:30 and so on)
- 0 */3 * * 1-5Every 3 hours on weekdays only
- 0 1-23/3 * * *Every 3 hours starting at 01:00 instead of midnight
- 0 0 */3 * * *Spring @Scheduled (seconds first): every 3 hours
- 0 0 0/3 * * ?Quartz (seconds first, ? for day of week): every 3 hours
- cron(0 0/3 * * ? *)AWS EventBridge (6 fields, with year): every 3 hours
Questions
What is the cron expression for every 3 hours?
0 */3 * * *. Every 3 hours, on the hour.
Which timezone will it run in?
Crontab on a server uses the server clock (often UTC). In RunLater you pick the timezone on each scheduled request, and daylight saving changes are handled for you.
What if the job fails?
Plain cron does not retry. RunLater retries a failed request (non-2xx or timeout) with exponential backoff, up to 10 retries, and logs every attempt with the status code and response body.
Call a URL every 3 hours without running a server
Paste 0 */3 * * * into a RunLater scheduled request with your URL, method, headers and body. It runs in the timezone you choose, retries failures and logs every response.
Next steps: set up a cron job for a URL, pick the right timezone and see how failed runs are retried.