[05/13/2024 21:41:33 > 028a57: SYS INFO] Detected WebJob file/s were updated, refreshing WebJob
[05/13/2024 21:41:33 > 028a57: SYS INFO] Status changed to Starting
[05/13/2024 21:41:33 > 028a57: SYS INFO] WebJob singleton setting is False
[05/13/2024 21:41:33 > 028a57: SYS INFO] Run script 'run.cmd' with script host - 'WindowsScriptHost'
[05/13/2024 21:41:33 > 028a57: SYS INFO] Status changed to Running
[05/13/2024 21:41:34 > 028a57: INFO]
[05/13/2024 21:41:34 > 028a57: INFO] C:\local\Temp\jobs\continuous\TestJob\0kyvd1qs.yes>DemoWebJobs.WebJob.exe
[05/13/2024 21:41:34 > 028a57: SYS ERR ] Job failed due to exit code -2146232576
[05/13/2024 21:41:34 > 028a57: SYS INFO] Process went down, waiting for 60 seconds
[05/13/2024 21:41:34 > 028a57: SYS INFO] Status changed to PendingRestart
[05/13/2024 21:42:34 > 028a57: SYS INFO] Run script 'run.cmd' with script host - 'WindowsScriptHost'
[05/13/2024 21:42:34 > 028a57: SYS INFO] Status changed to Running
It continually restarts. Is this a documentation issue or a product issue? It runs locally as a console app, consuming the queue. Deploying as triggered, the job never is triggered when queue messages are present. In the Kudu console I can nav down to the job's config and it has the storage connection string.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 2b7b9f5c-4610-8cea-28d4-fea8ea03e7e1
Version Independent ID: cc09b46d-cd40-45e8-ed45-7a0e3bf4b100
Hi @BobbyMorris thanks for bringing this to our attention. We have assigned this issue to the author to review further and take the next course of action.
Under WebJobs as .NET Framework console apps, find the section Create a new WebJobs-enabled project. Follow the link to Use the WebJobs new-project template for an independent WebJob. Use the SDK template for a new project. Create a new resource group with a storage account. Add connection string to app.config as instructed by template. Now follow Deploy a WebJobs project. Specify the resource group previously used, new app service, publish with new app service in continuous run mode.
Check WebJob logs -
It continually restarts. Is this a documentation issue or a product issue? It runs locally as a console app, consuming the queue. Deploying as triggered, the job never is triggered when queue messages are present. In the Kudu console I can nav down to the job's config and it has the storage connection string.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.