Azure Web Job schedule time being ignored after successful deployment

0
votes

I have a handful of triggered Web Jobs I need to deploy, I've deployed one and everything looks good.

The next one I've deployed it seems to ignore the schedule time within the Settings.Job file for some strange reason, instead after the deployment has been successful it shows n/a within the Schedule column of the Web Job

My Settings.Hob file is:

{
  "schedule": "0 */15 * * * *"
}

Again nothing to out of the ordinary.

I've deleted the Web Job completely of Azure, done a fresh deployment and the issue still persists.

I've then decided to use Kudu and navigate to the Web Job directly and check the Settings.job, however when navigating to:

D:\home\data\jobs\triggered>

My recently deployed Web Job doesn't exists, yet it appears within the Web Job UI, I've also checked Continuous just to be on the safe side and again no reference there of it.

I can't seem to find any solutions on the web for this issue, has anyone experienced this?

1
azureazure-webjobs
how do you deploy your webjobs? – Ivan Yang
@IvanYang via Visual Studio, apologies I should have mentioned that. – Code Ratchet
did you create a console project in visual studio, then select publish as a wejob from visual studio, right? – Ivan Yang
@IvanYang that's correct – Code Ratchet
@IvanYang no rules in place to ignore the file, my first web job deployed successfully with no issues and that resides in the same visual studio project. I have just changed the Build Action from "none" to "content" and it now seems to be picked up and deployed. Weird that I never needed to set the Build Action on the first web job. – Code Ratchet

1 Answers

1
votes

The solution is that right click Settings.job file -> properties -> then for Build, select "content".

I just had this issue for one time(.net framework and .net core), next time, I don't need to set it to content.

It seems weird, if someone else knows the reason, please feel free to explain this behavior.