In PipelineController , we can set a flag disable_clone_task to re-use the scheduled task. Initially that task is in the draft mode, so this works on the first iteration of the scheduler. However, after the first iteration the scheduled task has its status set to completed , and the scheduler cannot not re-use it; it prints a warning 'Task cloning disabled but requested Task ... status=completed. Reverting to clone Task' and starts cloning the task. Is it intended? Do I need to manually reset the status of the scheduled task to created after each execution?