We have a long runtime triggered webjob.

We have a webjob project that is a timer based project. It runs locally (offline in VS2022 debugger), but we are using devops to build as a linux target ‘–runtime linux-x64’ and deploying to App_Data/jobs/triggered/Jobnamefolder/appfiles, and when deployed it does not appear to run, or at least there is no evidence the job exists – it is not shown on the webjobs page – more on that later.

We have an Azure Api App with a continuous WebJob running a .net 8 WebJobs SDK app with a Service Bus triggered function. The function can run for prolonged periods and we need to handle Azure infrastructure updates when the underlaying VMs are rebooted properly.