explain why some tasks don't get started in a job

[bmc-msft]

Let's assume we have a pool with only a single VM.

When we launch a libfuzzer basic template job for one hour, the fuzzing task will launch and run for one hour. Once any task in the job starts executing, the job timer begins. After one hour, the job is stopped. However, in this hour, the coverage and crash reporting tasks stay in the "scheduled" state until the job is eventually stopped because a VM never tried to start that task.

In this limited VM count example, the user is shown the task "stopped" successfully. While this is true, it would be more useful to say "this task never launched".