Changelog: Seqera Cloud

Feature updates and improvements​

• Data Studios:
  • Added data studio API endpoints to the OpenAPI spec.
• New dynamic page title for easy bookmarking.
• Free tier:
  • New organization types added to allow free tier users to monitor their usage and limits.
• Restore errorStrategy default Nextflow config for AWS and GCP launches. The Nextflow job now correctly terminates after pipeline completion.
• Improved error messaging when pipeline info can't be fetched indicates whether the issue is due to a missing resource, or failed authentication due to expired credentials.
• Azure jobs are now automatically terminated after all tasks are complete.
• Send only added/updated run parameters when launching a pipeline. This includes all defaults and parameters passed during the launch.
• Updated list of EC2 families with NVMe disks available.
• Upgrade to Angular 17
• Bump Nextflow launcher to 24.10.3

Bug fixes​

• Allow unsetting schemaName when editing a pipeline.
• Use preferred_username as fallback email field for OIDC login.
• Drop the last characters in job definition name, if longer than the prescribed limit.
• Compute environment creation form allows pre- and post-run scripts to be longer than the accepted value of 1024 characters.
• Prohibit duplicate Git credentials and tie-break on lastUpdated for existing duplicates. Going forward, preference is given to the credentials updated last in the situation when there are multiple candidates. Additionally a duplicate check is added when creating new credentials, to avoid new duplicate cases.
• Disable reset selection on data change in workflow list component.
• Take into account the alternative mainScript path.

Breaking changes​

• Restore errorStrategy and maxRetries default Nextflow config for AWS and GCP launches. Platform will not overwrite existing error strategy coded in the pipeline repository.
• If you want to automatically retry on task failures (e.g., from spot reclamations), you will now need to explicitly set errorStrategy and maxRetries.
• Automatic spot retries in AWS and GCP need to be actively enabled. Alternatively the generic failure is handled at the Nextflow level.

You can revert to the default setting used in Nextflow prior to 24.10 with the following configuration options:

aws.batch.maxSpotAttempts = 5
google.batch.maxSpotAttempts = 5

Set task.maxRetries to a non-zero value to restore Platform to prior behaviour.

How do I retry Spot failures while making them visible?

There is no mechanism in Nextflow to specifically report Spot retries. However you can set process.maxRetries = 5 to retry all failures (including Spot reclamations) a specified number of times before failure.

Feature updates and improvements​

• Data Studios:
  • Added data studio API endpoints to the OpenAPI spec.
• New dynamic page title for easy bookmarking.
• Free tier:
  • New organization types added to allow free tier users to monitor their usage and limits.
• Restore errorStrategy default Nextflow config for AWS and GCP launches. The Nextflow job now correctly terminates after pipeline completion.
• Improved error messaging when pipeline info can't be fetched indicates whether the issue is due to a missing resource, or failed authentication due to expired credentials.
• Azure jobs are now automatically terminated after all tasks are complete.
• Send only added/updated run parameters when launching a pipeline. This includes all defaults and parameters passed during the launch.
• Updated list of EC2 families with NVMe disks available.
• Upgrade to Angular 17
• Bump Nextflow launcher to 24.10.3

Bug fixes​

• Allow unsetting schemaName when editing a pipeline.
• Use preferred_username as fallback email field for OIDC login.
• Drop the last characters in job definition name, if longer than the prescribed limit.
• Compute environment creation form allows pre- and post-run scripts to be longer than the accepted value of 1024 characters.
• Prohibit duplicate Git credentials and tie-break on lastUpdated for existing duplicates. Going forward, preference is given to the credentials updated last in the situation when there are multiple candidates. Additionally a duplicate check is added when creating new credentials, to avoid new duplicate cases.
• Disable reset selection on data change in workflow list component.
• Take into account the alternative mainScript path.

Feature updates and improvements​

• Add AWS Forge support for Amazon Linux 2023.
• Deprecate Google Life Sciences API.
• Refactor reports file streaming over Agent connections.
• Bump Nextflow launcher to 24.10.0.
• Add name validation to custom containers during Data Studio session creation.

Bug fixes​

• Propagate EFS mount path to container volume.
• Include optimization data to launch request, if present.
• Correctly update user through profile page.
• Input form view not working for private GitHub repos during pipeline quicklaunch.
• Improve layout on large displays.
• Add missing permissions check to data studio checkpoint "Start as new" option.
• Workspace secrets not selected by default during pipeline quicklaunch with new launch form.
• Add volumes to data studio job definition.
• Users with "Maintain" role and lower can edit resource labels when launching with the new pipeline launch form.
• Do not register the "User" route if user personal workspace is disabled.
• Apply the old launch form behavior to the new launch form when launching a shared pipeline from a private workspace.
• Improved error messaging for expired Git credentials.

Seqera Cloud authentication updates​

Seqera Platform Cloud has migrated to a new authentication provider, which includes two major changes to the login flow.

Passwords for email login​

• Users signing in via email: The next time you sign in to Seqera Cloud, select the option to create a new account — "Create one" — and add a password for your existing account. All your existing account information will be preserved and all future sign-ins can be completed with your new password.

• Users using Github/Google sign-in: You are not required to define a password for your account and shouldn’t see any changes on your next sign-in.

Account linking​

Users that sign in with multiple accounts associated with the same email address: You will be prompted to optionally merge your accounts into a single account. This will merge all your work across the two different accounts into the same account and give you the option to sign in via either method of authentication.

If you choose not to merge accounts, you will not be prompted again. If you wish to merge accounts later, or would like to merge accounts with different email addresses, contact Seqera Support.

Feature updates and improvements​

• Data Studios now support GPUs.
• The pipeline parameters input form now supports JSON schema draft 2020-12.
• Augment Data Studios images with custom Conda environment.
• Data studio creation now includes YAML validation.
• Data Studios build stats are now included in the Dashboard.
• New data studios now include "Add only" and "Add and start" actions.

Bug fixes​

• Add back to login button in authentication error screen.
• Add custom token cookie login handler for Nextflow requests to receive authentication cookies.
• Data Studios UI fixes.
• Jedis connection pool config which caused potential instabilities.
• Improve Data Studios error messaging.
• Delete Data Studio checkpoint on build failure.
• Update default Data Studios tool versions.
• Failed Data Studios can now be deleted.
• Set launch form to parameters step view by default when a pipeline schema is present, regardless of specification.
• Dashboard persisted filters exclude workspace IDs the user no longer has access to.
• Do not fetch info for INVALID status pipelines, fetch for all other statuses including DISABLED.
• Fixed a problem with Azure Entra credential creation.
• Return an empty list of data studios when receiving an invalid status.
• Fallback to primary compute environment when launching a shared pipeline without an associated compute environment from a private workspace.

Feature updates and improvements​

• Quick Launch now accepts pipelines that do not have a branch named master.
• Improved query times on some clean up job queries.
• NF Launcher image is now by default pulled from cr.seqera.io public registry instead of quay.
• Data Studios: Data Studio sessions can now share mounted data across the same workspace.
• The new Launch Form is now available in Quick Launch and personal workspaces.
• Improved fetching of the cloud cost estimation for Google Cloud Platform's (GCP) spot instances.
• ECS container timeout configuration is now defaulted to 10 minutes (ECS_CONTAINER_CREATE_TIMEOUT=10m,ECS_CONTAINER_STOP_TIMEOUT=10m,ECS_MANIFEST_PULL_TIMEOUT=10m).
• New dashboard for Data Studios.

Bug fixes​

• If the revision wasn't specified in Quick Launch, schemas weren't correctly fetched.
• Retrieving managed identity IDs on updates resulted in the incorrect managed identity being displayed.
• Start in new tab from the Data Studio form didn't navigate back the main tab to Data Studios page.

Feature updates and improvements​

• Updated Azure service principal credentials.
• Data Studios: Add direct Data Explorer browse link to mounted data items.
• Data Studios: Make studio details page tabs routable.
• Data Explorer: Highlight invalid custom datalinks.
• Data Explorer: Remove folder validation.
• Define cache configuration once, only override changes.
• Disable AWS and Google Batch spot instance auto retry.
• Update 204 pipeline schema response description.
• Patch workflow revision.
• Render Parameters UI correctly with new schemas based on 2020-12 draft.
• Upgrade to Angular 16.
• Pipeline launch form: Delegate form creation to a form builder service.

Bug fixes​

• Connection to Redis SSL server.
• pairingId declaration in API schema.
• Copying empty list for cloud data links.
• Visual glitches in launch form.
• Datalink status always null.
• Update last used field in compute environment when creating a data studio job.
• Terminated by Tower error.

Bug fixes​

• Data Explorer: Enable task working directory navigation using Data Explorer in personal workspaces by adding routing.
• Remove -/+ increment buttons from numeric input components in Platform, including compute environment and launch form interfaces.
• Hide compute environment variables section actions when component is disabled (previously indicated that environment variables could be edited in this state).

Feature updates and improvements​

• Add global Nextflow configuration support in compute environments.
• Add flexibility for pipeline names in workspaces.
• Add tag propagation to launch templates.
• Add managed identities support for manual Azure Batch compute environments.
• Implement custom launch container logic.

Bug fixes​

• Improve workflow launch screen look and feel.
• Allow pipeline work directory to be changed during pipeline launch.
• Handle special characters in prompt modal confirmation text regex.

Version bumps​

• Bump nf-launcher:j17-24.04.4
• Bump codecommit 0.2.1

Feature updates and improvements​

• Add code blocks syntax highlighting and background color.
• Role selector dropdown detail.
• Update navbar help and support links.

Bug fixes​

• Disable launch form submit button during form validation.
• Update team guest welcome email visuals and copy.
• Tag search with underscore.
• Add missing gap between shared badge and labels.
• Data Studios template override.
• View credentials back navigation.
• Data Explorer search bar misalignment.
• Parameters merging in schema form without key in schema.

Version bumps​

• Bump nf-launcher:24.04.3

Feature updates and improvements​

• Managed identities: Allow organization members and collaborators to list managed identities.
• Data Studios: Data studio user activity auditlog.
• Data Studios: Delete checkpoints.
• Data Studios: Rename checkpoints.
• Data Explorer: Multi-download functionality.