Whenever the scheduling fields of an already scheduled task are changed,
the old scheduled execution, re-creates a new file in the spooler with the old scheduling values.
Thus, multiple files, with different execution scheduling will live in the spooler, generating confusion and unwanted executions.
A workaround is to manually stop the task (thus removing the file in the spooler), before changing the values.
This could be also the possible solution. Whenever an update is required for a task, the task is automatically stopped before the update, so that no trailing files are left in the spooler.
Whenever the scheduling fields of an already scheduled task are changed,
the old scheduled execution, re-creates a new file in the spooler with the old scheduling values.
Thus, multiple files, with different execution scheduling will live in the spooler, generating confusion and unwanted executions.
A workaround is to manually stop the task (thus removing the file in the spooler), before changing the values.
This could be also the possible solution. Whenever an update is required for a task, the task is automatically stopped before the update, so that no trailing files are left in the spooler.