Dear Team,
(ASIS:) With the current settings, one can't configure tasks and phases to be non-restartable.
(TOBE:) Configure tasks and phases to be non-restartable.
(Question/TODO:) Please check if this property can be set. If it can't, we'll need an impact assessment that considers workflow principles like DAGs.
Potential gains:
-Easier, more intuitive process design
-More regulated workflow
-Allowing identifying possible rollback points easier while maintaining the original process flow
-Maintaining DAG principle
-Clear maintenance trail
-Concurrency safety for parallel processes
Thanks and regards,
Peter
by: Peter S. | 25 days ago | Templates & Releases
Comments
Thank you for the suggestion. To better understand the use case, we have a few questions:
1/ Can you walk us through a specific situation where a task or phase being restarted caused a problem? What had already happened before the restart, and what went wrong as a result?
2/ If a task marked as non-restartable were to fail, what should happen to the downstream tasks and the release itself? Should the release abort, pause for manual resolution, or continue past the failed task?
We want to understand the use case better and the possible solution here - if a permission change that prevents certain users from restarting tasks, or a strict policy set on the task itself that blocks restarts regardless of who is attempting them would work better or more universal.