Azure-docs: Possible Status for Webjobs

[AlissonRS]

Hello!

I'd like to know if there a list of all possible "Status" a Webjob can go, and what they mean.

Just as an example, what does it mean when a triggered webjob is on "Aborted" status? I want to monitor the webjobs, but I'm not sure what statuses I should be concerned, what they mean.

The doc I was reading and hoping to find the answer to this question is here:

https://docs.microsoft.com/en-us/azure/app-service/webjobs-create

Thanks,
Alisson

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 24523dbf-010f-b844-5ff0-88192eac8849
• Version Independent ID: d7ef5962-d94c-96d0-bf08-1efffc6d402b
• Content: Run Background tasks with WebJobs - Azure App Service
• Content Source: articles/app-service/webjobs-create.md
• Service: app-service
• GitHub Login: @ggailey777
• Microsoft Alias: glenga;msangapu;david.ebbo;suwatch;pbatum;naren.soni;

[mimckitt]

@AlissonRS please provide us a link to the documentation you are referring to so we can better assist.

[AlissonRS]

@MicahMcKittrick-MSFT sorry, here you are (I also updated my question):

https://docs.microsoft.com/en-us/azure/app-service/webjobs-create

[mimckitt]

Thanks for that! I will assign to @BryanTrach-MSFT to look into this further

[BryanTrach-MSFT]

@AlissonRS Below is a list of common webjob statues and a brief description. I hope this answers your question.

• Initializing - The site was just started and the WebJob is doing it's initialization process.
• Starting - The WebJob is starting up the process/script.
• Running - The WebJob's process is running.
• PendingRestart - The WebJob's process exited (for any good or bad reason) in less than 2 minutes since it started, for a continuous WebJob it's considered that something was probably not right with it (some exception during start-up probably as mentioned by Victor), at this point the system is waiting for 60 seconds before it'll restart the WebJob process (hence the name "pending restart").
• Stopped - The WebJob was stopped (usually from the Azure portal) and is currently not running and will not be running until it is started again, best way to see this is as disabled.
• Aborted - This can occur for a number of reasons such as the webjob running for 20 minutes and hitting the timeout marker.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

[AlissonRS]

@BryanTrach-MSFT thanks for your help, that was very helpful.

There are continuous and triggered webjobs. In what state should a triggered webjob be when it's not processing/running?

e.g a webjob that is triggered by a storage queue, but there has not been any messages enqueued for a few days, therefore the webjob has not been running since then. What is the status the webjob will be while waiting for new messages after a few days?

Thanks!
Alisson

[BryanTrach-MSFT]

@AlissonRS Good catch. The status for that would be 'Ready', which means the webjob is in a ready state to be triggered and complete the request.