Azure Webjob timer trigger does not fire

Question

We have two deployments (Prod and Test) of Azure Webjob running with TimerTrigger. Both the web apps have single instance. According to this article, TimeTriggers use single

Answer 1

You're right, you have to use different storage accounts.

From the documentation:

Behind the scenes, TimerTrigger uses the Singleton feature of the WebJobs SDK to ensure that only a single instance of your triggered function is running at any given time. When the JobHost starts up, for each of your TimerTrigger functions a blob lease (the Singleton Lock) is taken. This distrubuted lock ensures that only a single instance of your scheduled function is running at any time. If the blob for that function is not currently leased, the function will acquire the lease and start running on schedule immediately. If the blob lease cannot be acquired, it generally means that another instance of that function is running, so the function is not started in the current host. When this happens, the host will continue to periodically check to see if it can acquire the lease. This is done as a sort of "recovery" mode to ensure that when running steady state, if an instance goes down, another instance notice and pick up where the other left off.

If you look at the implementation of the locking mecanism (StorageScheduleMonitor.cs):

• The job acquires a lock (blob) inside the container.
• The blob is located inside a particular directory (based on the HostId).
• the name of the blob is not configurable.

So based on @volodymyr-bilyachat answer, there are two possibilities:

• Having separated storage accounts: makes sense if you have a storage account per environment (dev/staging/prod)

• Specifying the HosId property of the JobHostConfiguration class:

  var config = new JobHostConfiguration();
  config.HostId = "dev|staging|prod";
  

Answer 2

Use different storage accounts or set host

var config = new JobHostConfiguration();
config.HostId = "dev|prod"
var host = new JobHost(config);
host.RunAndBlock();

Answer 3

Make sure that you have Always On enabled on your Web App if you use TimerTrigger.