How to Schedule Functions with CRON Using TimerTrigger in Azure

You can schedule Functions in Azure using the @TimerTrigger annotation along with a six-part CRON expression. This allows you to schedule Functions to run tasks at specific times, such as every five minutes or at 9:30 AM on weekdays. TimerTrigger helps you schedule Functions for jobs like backups, ETL, report generation, cleanup, and sending notifications. It’s important to configure the schedule Functions settings correctly to ensure your function runs when intended. Dynamic scheduling enables you to adjust your schedule Functions as your requirements evolve.

Key Takeaways

• Use TimerTrigger with a six-part CRON expression. This helps you schedule Azure Functions in a reliable way. It also gives you more options for timing.

• Put your CRON schedule in app settings or config files. This lets you change the time without changing your code.

• Always check your CRON expression with tools that use six fields. This helps you avoid mistakes and missed runs.

• Set the WEBSITE_TIME_ZONE setting. This makes your functions run in your local time zone, not UTC.

• Follow best practices like writing stateless functions. Handle errors and watch your runs. This keeps your schedules working well.

TimerTrigger and CRON Basics

What Is TimerTrigger?

TimerTrigger lets you run your Azure Function on a schedule. You do not need to start the function yourself. Instead, you set up a schedule, and Azure runs the function for you. This works well for tasks like sending daily reports, cleaning up data, or running backups.

TimerTrigger uses a special schedule called a CRON expression. This schedule tells Azure when to run your function. You can set it to run every minute, every hour, or even just once a year. The TimerTrigger works by storing the schedule in Azure Storage. When the time comes, Azure reads the schedule and starts your function. By default, TimerTrigger uses the UTC timezone, but you can change this in your settings.

You get a reliable way to run code without needing to watch over it. TimerTrigger also tries to make sure only one instance of your function runs at a time. If your function takes longer than expected, the next run waits until the first one finishes. This helps prevent problems from overlapping runs.

Tip: TimerTrigger works best for jobs that do not need to run at the exact second. Sometimes, a run might get skipped if your app restarts or if the function takes too long.

Six-Field CRON Format

Azure Functions use a six-field CRON format to set the schedule. Each field controls a part of the time when your function runs. The fields are: second, minute, hour, day, month, and day of the week.

Here are some example CRON expressions and what they do:

You can use special characters like * for "every value," / for intervals, and - for ranges. For example, 0 */5 * * * * means "run every five minutes." All times use UTC, so remember to adjust for your local time if needed.

Schedule Functions with TimerTrigger

Create a TimerTrigger Function

You can schedule Functions in Azure by making a TimerTrigger function. You do not need special software to begin. You just need an Azure account. Here is how you make a TimerTrigger function in the Azure Portal:

1. Log in to the Azure Portal with your Microsoft Azure account.

2. Go to the Azure Functions overview page.

3. Click the 'Function' tab and pick 'Create' to make a new function.

4. Choose 'Timer Trigger' from the list of triggers.

5. Type a name for your function.

6. Set the schedule with a CRON expression, like 0 */1 * * * * to run every minute.

7. Click 'Create' to finish making your function.

8. After it is made, open the function's overview page. Here, you can:

   • Use 'Code + Test' to write or change your code.

   • Use 'Integration' to set up input and output bindings.

   • Use 'Monitor' to see when your function runs.

   • Manage access with 'Function Keys'.

9. In 'Code + Test', you can see and change the TimerTrigger template.

10. Test your function in the portal by clicking 'Test/Run' and watch what happens.

11. Check the overview page to see how many times your function ran and its status.

Tip: You do not need to install anything extra to schedule Functions in the Azure Portal. Everything works in your browser.

Add the CRON Expression

When you schedule Functions, you must add a CRON expression to set the time. You can put the CRON expression in your code, but using settings makes it easier to change later. Here is how you do this:

1. In your code, use the TimerTrigger attribute and point to a config key with %KeyName%. For example:

[FunctionName("MyTimerFunction")]
public void Run([TimerTrigger("%MyTimerCRON%")] TimerInfo myTimer, ILogger log)
{
    log.LogInformation($"Function ran at: {DateTime.UtcNow}");
}

1. When working locally, add the CRON expression to the local.settings.json file under "Values":

{
  "Values": {
    "MyTimerCRON": "0 */5 * * * *"
  }
}

1. When you move to Azure, add the same key and value in the Function App's Configuration tab.

2. This way, you can change the schedule without changing your code. You only update the settings.

Note: If you remove the CRON expression from the settings, your function will not run and may show an error. Always keep a good CRON value in your settings.

Use VSCode or Portal

You can schedule Functions with Visual Studio Code (VSCode) or the Azure Portal. Each way has its own steps and benefits.

Using Visual Studio Code

1. Open VSCode and pick 'Azure Functions: Create New Project' from the command palette.

2. Choose an empty folder for your project.

3. Pick your programming language, like Python or C#.

4. Pick the right interpreter if you need one.

5. Choose the 'Timer Trigger' template.

6. Type a name for your function, like 'Demo-timer-trigger'.

7. Enter your CRON expression to set the schedule.

8. Add the function to your workspace.

9. Press F5 or click 'Start Debugging' to run or debug the function.

10. Pick or make an Azure Storage Account if asked.

11. Your function will start, and you can see logs in the output window.

You can also send your function to Azure by right-clicking the project and picking 'Deploy to Function App'. Follow the steps in the wizard.

Using the Azure Portal

The Azure Portal lets you make and manage TimerTrigger functions in your browser. You can write code, set the schedule, and watch your function without leaving the portal. But you cannot debug locally in the portal.

Comparing VSCode and Azure Portal

Tip: If you want to test and debug before sending to Azure, use VSCode. If you want to make quick changes or watch your function, use the Azure Portal.

You can schedule Functions both ways. Pick the way that works best for you. Always keep your CRON expressions up to date in your settings to avoid errors.

Test and Validate CRON Schedules

Validating CRON Expressions

Before you deploy your Azure Function, you should always check your CRON expression. This step helps you avoid mistakes that can stop your function from running at the right time. You can use online tools to make this process easy and reliable.

The elmah.io Cron Expression Parser and Creator Tool is a free online tool that helps you check your CRON expressions. You can paste your CRON schedule into the tool, and it will show you what the schedule means in plain language. It also displays the next times your function will run. This makes it simple to see if your schedule matches your needs.

You can also try the Workik.com Cron Job Expression Generator. This tool uses AI to help you create, test, and validate CRON expressions for Azure Functions. It supports complex schedules and gives you error reports if something is wrong. Workik.com even works with CI/CD pipelines, so you can add it to your workflow. Many users trust this tool for production because it helps prevent scheduling errors.

Tip: Always use a tool that supports the six-field CRON format for Azure Functions. Some tools only support five fields, which can cause problems.

Common Mistakes

You might run into some common mistakes when you write CRON expressions for Azure TimerTrigger functions. One of the biggest mistakes is using the traditional five-field CRON format. Azure Functions need a six-field format that includes seconds. If you use only five fields, your function will not run as expected. For example, 0 0 */11 * * will not work, but 0 0 */11 * * * will.

Another mistake is using online CRON generators that do not support the Azure six-field format. These tools can give you the wrong expression, which leads to confusion and missed triggers. Always double-check that your tool supports Azure Functions.

You should also watch out for environment issues. If you use an App Service Plan, make sure the 'Always On' setting is enabled. If you use a Consumption Plan, your triggers must sync correctly. Sometimes, triggers do not fire because of these settings, not just because of the CRON expression.

Note: Microsoft’s documentation has more tips on troubleshooting timer triggers. Always check your hosting plan and sync settings if your function does not run.

Advanced Scheduling Options

Dynamic Configuration

You can make your Azure Functions more flexible with dynamic configuration. Instead of putting the CRON expression in your code, use environment variables or config files. This way, you can change the schedule without redeploying your function. To do this, put the app setting name inside percent signs in your TimerTrigger. For example, use %DynamicSchedule% in your TimerTrigger. When you are developing, add the schedule to your local.settings.json file under Values:

{
  "Values": {
    "DynamicSchedule": "0 */5 * * * *"
  }
}

When you move to production, set the DynamicSchedule key in the Azure portal Application Settings. You can update the CRON schedule anytime, and Azure Functions will notice the change right away. This makes it easy to manage and update your schedule Functions.

Tip: For even more control, you can use Azure App Configuration or an outside database to store your schedules. If you do this, you might need to restart your function app when you change the schedule.

Timezone Settings

Azure Functions use the UTC time zone by default. This can make your scheduled tasks run at odd times if you want them to follow your local time. You have two main ways to fix this:

• Change your CRON expression to match UTC time.

• Set the WEBSITE_TIME_ZONE environment variable in your Function App settings. For example, use Eastern Standard Time or India Standard Time.

When you set WEBSITE_TIME_ZONE, Azure Functions will use your local time zone for the CRON schedule. This makes it much easier to schedule Functions at the right local time and you do not have to change times by hand.

If you need to run the same function at different times for different time zones, make more than one timer trigger with different CRON expressions. Each trigger can call the same method so you do not have to write your main logic again.

Note: The WEBSITE_TIME_ZONE setting works for the whole Function App. All timer triggers in that app will use the same time zone.

Troubleshooting and Best Practices

Fixing Schedule Issues

You might have some problems when you schedule Azure Functions with TimerTrigger. Knowing how to find and fix these problems helps your functions work on time.

• CRON Format Errors: Azure Functions need a six-part CRON expression. If you use only five parts, your function will not work. Always check your CRON expression with a tool that uses six fields.

• Timezone Confusion: If your function runs at the wrong time, check the WEBSITE_TIME_ZONE setting. Make sure it matches your local time zone if you do not want to use UTC.

• Missed or Delayed Runs: Sometimes, your function does not run after you deploy or move it. This can happen in some environments, like .NET isolated on Linux Consumption plans. You can start the function by visiting it in the Azure Portal. Cold starts or not enough resources can also cause delays, especially in Consumption Plans.

• Trigger Sync Issues: After you deploy your function, triggers might not sync right away. Use the "Diagnose and solve problems" tool in the Azure Portal to check for sync issues or missed runs.

• Immediate Runs After Deployment: If your function runs right after deployment, Azure is catching up on missed runs. You can check if a run is a catch-up by using TimerInfo.IsPastDue in your code.

Tip: Always keep your project references and packages updated. This helps stop problems with timer triggers not working.

Here is a quick troubleshooting table:

Best Practices

You can make your scheduled functions work better and be easier to manage by following these best practices:

• Move CRON Expressions to Configuration: Put your CRON schedules in app settings or config files. This lets you change schedules without changing code or redeploying.

• Write Stateless and Idempotent Functions: Make sure your function can run more than once without causing problems. This helps if Azure retries a run or catches up after downtime.

• Handle Errors and Retries: Add error handling so your function can recover from failures. Use logging to track when and why errors happen.

• Organize Functions by Needs: Group functions with the same schedules or settings together. Use different function apps if you need different time zones or permissions.

• Monitor and Test Regularly: Use Azure Monitor and Application Insights to watch your function runs. Test your CRON expressions with trusted tools before you deploy.

Following these steps helps keep your Azure Functions working well and makes it easier to change schedules when you need to.

---

To set up scheduled Functions, use the TimerTrigger attribute with a six-part CRON expression. Make sure your CRON expression has seconds so it works right. Put your schedule in app settings. This lets you change times without touching your code. If you follow best practices, your functions will be simple to manage and will work well.

If you want to learn more ways to schedule Functions, check out Microsoft’s official docs and sample code for TimerTrigger.

FAQ

How do you update the schedule for a TimerTrigger function?

You can change the CRON expression in your app settings or configuration file. Azure Functions will use the new schedule right away. You do not need to redeploy your code.

What happens if you use the wrong CRON format?

Azure Functions will not run your function. You may see errors in the logs. Always use a six-field CRON expression for TimerTrigger.

Can you run a TimerTrigger function on demand?

Yes. You can use the "Test/Run" button in the Azure Portal to run your function right away. This helps you test your code without waiting for the schedule.

How do you set the function to run in your local time zone?

Set the WEBSITE_TIME_ZONE setting in your Function App. Azure will use this time zone for all TimerTrigger schedules in that app.

What should you do if your function does not run as expected?

Check your CRON expression, app settings, and logs. Make sure your app is running and triggers are synced. Use Azure’s troubleshooting tools for more help.