Home โบ Azure Functions โบ Every 30 seconds
Azure Functions cron expression: every 30 seconds
To run a Azure Functions job every 30 seconds, use:
*/30 * * * * *Every 30 seconds.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Twice a minute, using the seconds field that Unix cron lacks. Only schedulers built into the application, like Quartz and Spring, can express it; system cron and cloud schedulers cannot.
- Fast health probes
- Refreshing live counters
- Draining a small outbox table
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, 00:00:30 |
| 3 | Fri, 01 Jan 2027, 00:01:00 |
| 4 | Fri, 01 Jan 2027, 00:01:30 |
| 5 | Fri, 01 Jan 2027, 00:02:00 |
| 6 | Fri, 01 Jan 2027, 00:02:30 |
Every 30 seconds in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | */30 * * * * * |
| Quartz | 0/30 * * * * ? |
| Spring | */30 * * * * * |
| node-cron | */30 * * * * * |
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("*/30 * * * * *")] 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
- Timers support second precision. Schedules that fire more than once a minute are not monitored by default (UseMonitor defaults to false).
- NCRONTAB has a leading seconds field: 0 */5 * * * * runs every five minutes at second 0, while */5 * * * * * runs every five seconds.
- 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
If a job takes more than 30 seconds, runs will overlap or be skipped depending on the scheduler. In Spring use fixedDelay when you want a gap after the job finishes.
Frequently asked questions
How do I run a Azure Functions job every 30 seconds?
Use */30 * * * * *. Every 30 seconds.
What is the every 30 seconds cron expression in other systems?
Quartz: 0/30 * * * * ?; Spring: */30 * * * * *; node-cron: */30 * * * * *. 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.