5
votes

I'm trying to run WebJob as a console app, It works When I add RunOnStartup = true, but I need that it works just with TimerTrigger.

this is my code

public static void Main()
{
  JobHostConfiguration config = new JobHostConfiguration();
  config.UseTimers();
  JobHost host = new JobHost(config);
  host.RunAndBlock();
} 

public static void TimerJob([TimerTrigger("0 0 8 * * *")] TimerInfo timerInfo)
{
    Console.WriteLine("Job Work");
}

What do I need to make this code work?

3
What doesn't work specifically? You've set up a schedule that will run once a day at 8 AM, so it might be that it's not 8 AM yet? Recommend turning on Verbose logging locally - the JobHost will then print the execution schedule to the Console on startup, so you can see when it will next run.mathewc
You can turn on Verbose console logging via config.Tracing.ConsoleLevelmathewc
I added config.Tracing.ConsoleLevel = System.Diagnostics.TraceLevel.Verbose; And it return this : "The next 5 occurrences of the schedule will be: 1/8/2016 8:00:00 PM" However the method never runsrd98
Sorry, Return "The next 5 occurrences of the schedule will be: 1/8/2016 8:00:00 AM"srd98

3 Answers

3
votes

This behavior was due to an issue in TimerTrigger which has been fixed in the v1.0.1 release that is now live on Nuget.

The issue was that we were using UTC time internally when scheduling occurrences, rather than Local time as you'd expect. While this could cause confusion when running locally, your job would still run correctly on schedule in Azure.

However, this issue has been fixed now.

3
votes

This might not be the answer to your specific problem but it answers the very same question. I noticed that it wont find TimerTrigger functions in the Program class. When running it i just get the

Development settings applied

No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. config.UseServiceBus(), config.UseTimers(), etc.).

Job host started

After putting them in Function class it triggered just fine.

2
votes

First of all, add the JobHostConfiguration Tracing as described here in the Local Development section. Otherwise you won't see the Console text. If you are running locally, you can always set a breakpoint too.

Keep also in mind that the TimerTrigger uses the Web App Timezone when running on Azure or your computer Timezone when running locally. To define the Web App timezone, follow these steps.