We have a variety of web applications and web jobs (both Triggered and Continuous) spread across a number of environments.
One of the Triggered WebJobs was recently updated and was deployed successfully to our dev environment, however in QA and UAT the webjob status is showing as "Initializing" and will not exit this state after several redeploys and stopping / restarting the webapp.
The logs in the webjob dashboard simply show a single line
[08/20/2019 00:01:28 > 40ecf7: SYS INFO] Status changed to Initializing
There is no process running that I can see in Kudu (there is one for the main webapp and another continuous webjob we have), and if I go into Kudu, Debug Console and go to the Jobs/Triggered/DataSync (name of this webjob) folder and manually type run.cmd, then the job runs fine.
I've also tried deleting the Jobs folder and redeploying but still no luck. Any ideas?
