Home โบ Azure Functions โบ Every 6 hours
Azure Functions cron expression: every 6 hours
To run a Azure Functions job every 6 hours, use:
0 0 */6 * * *At minute 0, every 6 hours.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Four runs a day at 00:00, 06:00, 12:00 and 18:00. A popular backup and report rhythm.
- Incremental backups
- Re-crawling sitemaps
- Recomputing leaderboards
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 00:00:00 |
| 2 | Fri, 01 Jan 2027, 06:00:00 |
| 3 | Fri, 01 Jan 2027, 12:00:00 |
| 4 | Fri, 01 Jan 2027, 18:00:00 |
| 5 | Sat, 02 Jan 2027, 00:00:00 |
| 6 | Sat, 02 Jan 2027, 06:00:00 |
Every 6 hours in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 0 */6 * * * |
| Quartz | 0 0 */6 * * ? |
| Spring | 0 0 */6 * * * |
| Crontab | 0 */6 * * * |
| Kubernetes | 0 */6 * * * |
| AWS EventBridge | 0 */6 * * ? * |
| Jenkins | H */6 * * * |
| GitHub Actions | 0 */6 * * * |
| node-cron | 0 */6 * * * |
| Apache Airflow | 0 */6 * * * |
| Google Cloud Scheduler | 0 */6 * * * |
Need to translate a different expression? Use the cron converter.
Ready-to-use Azure Functions config
Drop this into your project. The expression is the one above.
[Function("MyTimer")]
public void Run([TimerTrigger("0 0 */6 * * *")] TimerInfo timer)
{
// ...
}WEBSITE_TIME_ZONE=Eastern Standard Time # Windows name; Linux uses America/New_York
# Without it, NCRONTAB runs in UTC.The Azure Functions fields, in order: second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
Things to watch out for in Azure Functions
- NCRONTAB has a leading seconds field: 0 */5 * * * * runs every five minutes at second 0, while */5 * * * * * runs every five seconds.
- The format is {second} {minute} {hour} {day} {month} {day-of-week}; five fields are accepted too. The default time zone is UTC.
- Azure Functions evaluates NCRONTAB in UTC unless the WEBSITE_TIME_ZONE app setting is set; with it, the schedule adjusts for daylight saving. The setting is not supported on Linux Consumption or Flex Consumption plans.
The common mistake with this schedule
The hours are fixed on the clock, not relative to when you deployed. Deploying at 07:00 does not make the next run 13:00.
Frequently asked questions
How do I run a Azure Functions job every 6 hours?
Use 0 0 */6 * * *. At minute 0, every 6 hours.
What is the every 6 hours cron expression in other systems?
Quartz: 0 0 */6 * * ?; Spring: 0 0 */6 * * *; Crontab: 0 */6 * * *. The table on this page lists every dialect.
Which time zone does Azure Functions use for this schedule?
Azure Functions evaluates NCRONTAB in UTC unless the WEBSITE_TIME_ZONE app setting is set; with it, the schedule adjusts for daylight saving. The setting is not supported on Linux Consumption or Flex Consumption plans.