Seqera Platform Feature Requests

On resume, Platform will increment any integers at the end of a run name that matches the regular expression _\d+$. If a user chooses a run name that happens to match this pattern, e.g. "myRun_ProjectFoo_20251105", or "wgs_sample_2459245", and the resumed run will corrupt this potentially useful run name by incrementing the trailing integer. It would be helpful if Platform uses an internal identifier for tracking resumed runs and/or removes the uniqueness constraint on run names.

I would like to use SSH keys for cloning Bitbucket-hosted pipeline repositories instead of tying credentials for a specific user. This would help avoid tying credentials to one person and improve security.

To evaluate pipeline parameters early we need a way of accessing the schema in a private pipeline outside of Seqera Platform. Since the platform has already retrieved the schema, it would be good to have an API for retrieving the schema and using internally, e.g. GET /workflows/${workflowId}/schema returning a JSON body. We could then use it in out-of-platform tools (e.g. nextflow launch , Tower CLI, Node-RED) for validation of pipeline parameters early.

When launching larger pipelines with many parameters, it is possible to hit the limit imposed by Platform, giving the error: ParamsText field too big - Max allowed size 20480 characters When this limit is reached, it can become difficult to launch the pipeline. Is it possible to increase or remove this limit?

I would like the ability to interactively select lower-level directories (from the bucket or custom data-link) for mounting to the Studio session. This would help manage a large numbers of directories without cluttering the interface.

Workspace administrators can further customize dynamic resource labels with prefixes, suffixes, and concatenations supported with dash and underscore separators ( - and _ respectively) to provide increased flexibility and better support organizational standards. Concatenation: * specific-user-and-workflow = "${userId}_${workflowId}" * specific-wksp-user-and-workflow = "${workspaceName}-${userName}-${workflowId} Prefixes: * custom-prefix = JohnDoe_${workflowId} Suffixes: * custom-suffix = "${workflowId}_mycompanyname"

Currently there are two ways to launch a pipeline via the API: Populate the body of a POST /workflow/launch request , which requires getting a number of details such as the compute environment and configuration Create an action and POST /actions/${actionId}/launch , which only take pipeline params as options It would be nicer to reconcile the two and have a simpler flow: Create pipeline on Seqera Platform Launch specified pipeline using an endpoint, e.g. POST /pipeline/${pipelineId}/launch Importantly you would only be able to modify a very limited subset of options with this option, e.g. the pipeline parameters. This would save the automation developer the time and effort in writing a number of requests to GET settings before launching a pipeline via automation. The revision, compute environment, working directory, staging options and many other settings would be fixed and require addition of a new pipeline for a launch. This has some overlap with some other feature requests such as: API equivalent of this feature request

I need an integration with Benchling that allows launching and monitoring pipelines directly from Benchling.

I'd like to be able to chain pipelines together within Seqera Platform, and not rely on an external service such as lambda functions to chain demultiplex => rnaseq => differentialabundance together for example

Update the current user role permissions to manage more fine-grained permissions (Role Based Access Control, etc).