Seqera Platform Feature Requests

In the Seqera Platform, when a pipeline execution is interrupted by a failure or other reasons, incomplete tasks may linger in inconsistent states (e.g., running, submitted), causing confusion as the pipeline execution is terminated. The intended outcome is a systematic 'reset' of the status for incomplete tasks when the pipeline execution is terminated. This involves changing the status of all tasks not in 'COMPLETED' or 'FAILED' states to 'ABORTED'. This adjustment ensures clarity and coherence in the status of tasks, eliminating confusion for users and aligning with the expected termination of the pipeline execution.

On a run detail page, the menu dropdown has an option called "Save as pipeline". However, if the run was launched outside of Seqera Platform (ie. nextflow run -with-tower ) this does not work. The UI is not intuitive - an error is thrown to the browser console and "nothing happens" in the front end. Suggestion is to remove this option from the dropdown completely on such runs, and add an admonition to the docs here: https://docs.seqera.io/platform/23.3.0/monitoring/overview#save-run-as-pipeline See https://community.seqera.io/t/save-as-pipeline-requirements/375 for context.