The RunTask action is best suited for batch job processes that will perform the work and then stop. As an example, if you have a RunTask process, when the work comes into the queue then the task pulls the work from queue, performs the desired work, and exits.
You can randomly distribute tasks across the cluster by allowing the task placement strategy using RunTask. In that case, a single instance will get the appropriate number of tasks. You can customize the task placement strategy and constraints to use RunTask.
Manually running the task is ideal in some situations. Let's say you have developed a task but you don't want to deploy this task with the service scheduler. If your task is a periodic batch job or one-time ...
