BackendBench
Coffee

Home โ€บ Azure Functions โ€บ Every 3 hours

Azure Functions cron

Azure Functions cron expression: every 3 hours

To run a Azure Functions job every 3 hours, use:

0 0 */3 * * *

At minute 0, every 3 hours.

Your week at a glance
fewer more runs

Upcoming runs

#LocalUTCFrom now

Copy-ready code

Why use this schedule

Eight runs a day: 00:00, 03:00, 06:00 and so on. Handy when you want regular coverage without hourly load.

First runs, as an example

Starting from 1 January 2027, evaluated in UTC:

#Date and time (UTC)
1Fri, 01 Jan 2027, 00:00:00
2Fri, 01 Jan 2027, 03:00:00
3Fri, 01 Jan 2027, 06:00:00
4Fri, 01 Jan 2027, 09:00:00
5Fri, 01 Jan 2027, 12:00:00
6Fri, 01 Jan 2027, 15:00:00

Every 3 hours in every dialect

SystemExpression
Azure Functions (this page)0 0 */3 * * *
Quartz0 0 */3 * * ?
Spring0 0 */3 * * *
Crontab0 */3 * * *
Kubernetes0 */3 * * *
AWS EventBridge0 */3 * * ? *
JenkinsH */3 * * *
GitHub Actions0 */3 * * *
node-cron0 */3 * * *
Apache Airflow0 */3 * * *
Google Cloud Scheduler0 */3 * * *

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.

Timer trigger (C#, isolated worker)
[Function("MyTimer")]
public void Run([TimerTrigger("0 0 */3 * * *")] TimerInfo timer)
{
    // ...
}
Time zone (app setting)
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

The common mistake with this schedule

Eight runs divide 24 evenly, but across a daylight-saving change the local gap can be two or four hours once a year.

Frequently asked questions

How do I run a Azure Functions job every 3 hours?

Use 0 0 */3 * * *. At minute 0, every 3 hours.

What is the every 3 hours cron expression in other systems?

Quartz: 0 0 */3 * * ?; Spring: 0 0 */3 * * *; Crontab: 0 */3 * * *. 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.

Similar Azure Functions schedules

More tools you might need