Improved error messages for insufficient permissions. API 403 Forbidden responses now include details about which specific permissions are missing, making it easier to troubleshoot authorization issues and grant appropriate access.
New AWS Batch compute environments can no longer be created with the deprecated EBS autoscaling feature enabled; use Fusion as the recommended alternative instead. Existing compute environments with EBS autoscaling will continue to work without changes.
Fixed an issue with pipeline optimization being unavailable for shared pipelines in personal workspaces.
Fixed an issue with pipeline optimization permission controls. Users with Launch permissions can now view optimization status and details in read-only mode, while users with Maintain or higher permissions can modify optimization settings.
Added the ability to configure a custom container repository path for Wave-built Studio images in workspace settings, providing greater control over where container images are stored and distributed.
Fixed an issue with interpolated values in dynamic resource labels (e.g., label-name=${workflowId}). Dynamic resource labels now work correctly when enabling the feature for all workspaces.
Fixed an issue with deleted workflows incorrectly counted toward organization quota limits. Active workflow counts now accurately exclude deleted workflows.
AWS Batch compute environments now use AmazonLinux2023-based AMIs by default, offering improved security (IMDSv2), better performance with gp3 EBS volumes, and a more recent kernel. Existing compute environments continue to function with AmazonLinux2 without changes, though we recommend migrating to newer compute environments before AmazonLinux2 reaches end-of-life in June 2026.
Fixed compute environment variables created without specifying a target environment (head or compute), which prevented the system from applying variables during workflow execution. The system now validates that at least one target environment is specified, preventing invalid configurations and providing clear error messages.
Fixed display issues with long helper text in pipeline schema forms. Helper text now wraps properly within form controls, improving readability for parameter descriptions with technical specifications or long value lists.
Fixed an empty launch form issue when launching shared pipelines from another workspace. The launch form now correctly retrieves and displays all pipeline configuration when launching shared pipelines across workspaces.
Fixed OIDC authentication errors with spaces or special characters that caused application crashes instead of displaying proper error messages. Authentication errors during login now display correctly to users, preventing application failures.
Added support for LakeFS Cloud in Data Explorer by enabling image preview and file upload functionality when using LakeFS Cloud as an S3-compatible storage provider.
Improved job failure handling in AWS Batch compute environments. Improved AWS Batch workflow behavior to automatically terminate unschedulable jobs instead of leaving them pending indefinitely, providing faster feedback when compute resources are insufficient for workflow requirements.
Added the g6e instance family to the list of AWS instances with NVMe storage.
Fixed an issue where plots and charts in MultiQC reports appeared as grey boxes instead of displaying correctly, ensuring all visualizations now render properly. MultiQC reports generated by pipeline runs now display complete quality control metrics and interactive charts without missing content.
Fixed an issue where YAML validation errors did not display immediately when importing Studio configurations from Git repositories, ensuring configuration issues are now visible as soon as the import completes.
Fixed an issue where AWS single VM compute environments could not pull container images from private Amazon ECR repositories, bringing them to feature parity with AWS Batch compute environments.
Fixed an issue with older pipeline launch records, where the system did not set the source type properly, resulting in the system failing to access the pipeline entity on launch.
Improved label inheritance when launching workflows via API to automatically apply predefined labels when omitting the labelIds field, aligning API functionality with the GUI and simplifying workflow relaunches.
Fixed an issue where changing the compute environment during workflow resume incorrectly updated the work directory path, causing failures because the workflow could not access cached results from the original run. The work directory now correctly retains the original value when resuming workflows with different compute environments.
Fixed an issue where the settings button in the usage overview widget incorrectly displayed workspace permissions in organization context, and improved workspace settings visibility to dynamically show or hide based on user permissions.
Fixed an issue where workspace settings buttons displayed incorrectly based on user permissions and context, ensuring the settings button now shows the appropriate organization or workspace settings based on the current view.
Added support for date-only formats in search queries, allowing you to search using simple dates (e.g., 2025-02-02) instead of full ISO-8601 datetime strings.
Fixed an issue where filtering for Azure credentials in Data Explorer only returned one credential type instead of all three available Azure credential types.
Fixed an issue where the Data Explorer link did not appear in Task View when configuring multiple AWS credentials with similar permissions in the workspace.
Fixed an issue where Seqera Compute environments did not apply proper EC2 instance type constraints, ensuring consistent compute environment behavior and preventing instance unavailability issues.
Fixed an issue where users could dismiss critical notifications about compute environment substitutions when relaunching pipelines, ensuring important status messages remain visible throughout the workflow.
Added support for image preview and file upload in Data Explorer when using Amazon S3-compatible API storage (for example, but not limited to, Cloudflare R2, MinIO, and Oracle Cloud).
Added support for MinIO object storage in Data Explorer, enabling users to browse, upload, and download files from MinIO instances using S3-compatible credentials.
Added the ability to read task logs on Azure Cloud from Azure Blob Storage after pipeline completion, ensuring logs remain accessible throughout the entire task lifecycle.
Updated the nf-launcher container versions from 25.04.6 to 25.04.8 for both standard and Docker-in-Docker variants.
Added an optional maxLength query parameter to workflow log endpoints (GET /{workflowId}/log and GET /{workflowId}/log/{taskId}) for improved log management.
Added user tracking fields to datasets and dataset versions. Datasets now include a lastUpdatedBy field to track the user who last modified the dataset, while dataset versions include a createdBy field to track the user who created each version.
Improved the visual consistency and user experience across workflow run interfaces. Updates include improved table borders, enhanced tooltip information, and refined pagination layouts in the containers view.