Creating an Execution Task while executing a job against failed targets
You can request the creation of an Execution Task when you execute a job against failed targets. This method of creating an Execution Task is the most appropriate when you are resolving problems that caused a job to fail on certain targets and are working towards successful job execution on all target servers.
An Execution Task created in this manner is automatically associated with the selected job, which is executed immediately. Target servers for the Execution Task include only the failed targets of the job, and no additional schedules are defined. These Execution Task settings can be modified only after the Execution Task has been created and the job has executed.
To create an Execution Task, you must have, at minimum, the ExecutionTask.Create authorization.
The Execution Task is added to the Jobs tree alongside the job with which it was associated. Its name is formed automatically by appending the date and time to the name of the original job. At this point, the Execution Task contains only two job runs — the selected original job run and the newly created job run that ran against the specified subset of target servers (that is, servers that returned errors, servers that returned warnings, or both).
If you need to repeat the execution of the job against failed targets after the Execution Task has been created, you can do so through the Execution Task, where all information necessary for tracking job progress towards full success is concentrated. Alternatively, you can modify the Execution Task and add recurring schedules for the job, so that it continues to progress towards successful completion on all targets.