Continuous web job-configurable timer trigger is not working in all instances

Question

I have created one continuous web job, I have a scenario like from the UI side user can update the schedule time so based on the latest schedule time web job should run.
For that I have prepared on method by using INameResolver and that is returning the CRON expression( Eg : %configurabletime%), so after deployment it is working fine but If I update schedule time from UI then web job is not executing with the latest value.

Answer 1

Welcome to Microsoft Q&A ! Thanks for posting this good question.

Apologies for my late response here.

Just to clarify, are those time triggered WebJob not triggering at all or not triggered on all scaled-out instances?
Scale - (Multi instance) - Available only for Continuous WebJobs. Determines whether the program or script runs on all instances or just one instance. The option to run on multiple instances doesn't apply to the Free or Shared pricing tiers.

Just to highlight:
Continuous - Runs on all instances that the web app runs on. You can optionally restrict the WebJob to a single instance. Setting: is_singleton
Triggered - Runs on a single instance that Azure selects for load balancing.

To fetch more details on the this, you could review these logs:

• App Logs as Verbose.
• Root of FTP: data\jobs\continuous\<yourJobName>\Job_log.txt
• Root of FTP: data\jobs\triggered{jobname}{jobrunid}
• Review WeJob log details from Diagnose and solve problems.
  

Kindly let us know if this helps or you have further questions, we would be more than happy to assist you.

Thanks for your patience and co-operation!