Hello, @Richard McMillian myloweslife
The behavior you’re experiencing is related to WebJob logs in Azure. Let’s get you back on track! To access the full logs for your WebJobs, follow these steps:
Azure Portal:
Go to the Azure portal.
Navigate to your App Service (where the WebJob is hosted).
Click on the WebJobs section.
Select the specific WebJob you’re interested in.
Under the WebJob details, click on Logs.
You’ll see a list of runs. Click on a specific run to view its details.
From there, you can download a text file containing the logs or explore logs for different runs using the breadcrumb link at the top of the page.
Kudu API:
The WebJob client makes calls to the Kudu API. You can find the list of functions in the WebJob by checking the console of your browser. Look for a call to:
https://<sitename>.scm.azurewebsites.net/azurejobs/api/functions/definitions?limit=100
This will give you a list of the functions in the WebJob.
Remember to enable website application diagnostics to capture the full logs for your WebJobs. You can configure the logs to go to either the file system (for 12 hours), table storage, or blob storage.
Hope this work for you.
Best regards,
Thomas Smith