Seqera Platform Feature Requests

We want to improve usability for selecting species as a pipeline input parameter from a large enumerated list (100+ items). The current drop-downs (based on the schema) are static and hard to navigate at this scale. Proposed enhancements: 1. Searchable dropdown with autocomplete/typeahead: type a partial species name (e.g., arabi ) and see relevant matches like arabidopsis thaliana . Ideally, the drop-down would dynamically filter items based on the typed input. 2. Dependent/inter-related dropdown menus: First drop-down filters by genus, second drop-down updates to show only species belonging to that genus. Default behavior (when no genus is selected) would show all species. Note: this would not be handled in the JSON schema, but rather as a front-end implementation in the Platform launch form (for example, triggering a different UI element if a parameter enum has more than 10 options).

We'd like to be able to mount an encrypted storage on Studios. Nextflow handles this via: aws { region = 'eu-west-1' client { storageEncryption = 'aws:kms' storageKmsKeyId = '<key id>' } }

Currently, when tasks fail with errorStrategy 'ignore', the workflow.failOnIgnore setting in Nextflow does not appear to be fully respected in Seqera Platform. Users expect that: If workflow.failOnIgnore = true , the run should be marked as failed, and this should trigger the standard "run failed" email notification. If workflow.failOnIgnore = false , the run should be marked as successful, even if some tasks were ignored. Optional (nice-to-have, not a priority): The failed run email could explicitly mention that the failure was due to ignored tasks. Additional UI indicators could highlight ignored-task failures, but the customer confirmed the current task overview is already sufficient.

It would be helpful to have an option to export Compute Environment details directly from the Seqera Platform UI (e.g., as a JSON or YAML file). This feature would simplify troubleshooting and support workflows. Instead of asking users to provide multiple or lengthy screenshots of their Compute Environment configurations, they could quickly export and share the details in a structured format.

I would like to download the nextflow.log file while the pipeline is still running from the run details page. I can see it is available in Data Explorer and I can download it from there while the pipeline is running, but the Download button on the pipeline page is greyed out. Having this available there directly would be nice quality of life improvement.

I want to store the per Studio .studio files in a separate S3 bucket from other compute environment workdir files to manage lifecycle policies more effectively.

I want to be able to pull secrets directly from AWS Secrets Manager instead of defining them within the platform.

When adding configuration options to the Nextflow configuration or parameter box in platform, I tend to easily miss syntax elements, like a closing } or " . Having some form of syntax highlighting and/or automatic formatting (indentation) option would be helpful to quickly spot errors for faster successful submission.

When creating a Studio sessions, it is possible to associate key-value resource labels to the session. These resource labels are displayed in the UI as tags, but the list of Studios does not provide the ability to filter or sort the studios based on the key or value of these labels. For larger workspaces with many studios, it would be helpful to subset the available sessions to those with particular keys and/or particular values.

It is possible for Nextflow to fail early which prevents the cleanup and log upload which would ordinarily happen at the end of a run. Without the logs on cloud storage, it becomes difficult to understand the failure. It is possible to force the upload by adding in a post-run script such as: echo "Copying log files:" for log in nf-*.log*; do aws s3 cp $log s3://my-bucket-name/debug-logs/ done It is possible to add this sort of fallback log upload as a built-in feature in Seqera Platform?