Seven Bridges knowledge centerDocumentation
Release notes
Back to All

Release Note - May 15, 2026

1 day ago by Rucha Kulkarni

Nextflow Improvements: Custom Head Instances and Network Restriction Support

General

This release introduces two enhancements to Nextflow head (executor) instance management: customizable compute resources at the app and task level, and compatibility with the existing project-level network restrictions. Together, these updates improve reliability, cost efficiency, and security for Nextflow workflows while preserving backward compatibility.

New Features

  • Customizable Head Job Instance for Nextflow Tasks: Nextflow tasks now support a dedicated “Nextflow Head Instance type” configuration under Task → Execution settings. When “Nextflow Multi-Instance Execution” is enabled, you can select a custom head instance type and adjust attached storage. App-level defaults can be defined in the app YAML configuration or managed via the public API, with changes reflected bidirectionally between YAML and the UI.
  • Network Restriction Compatibility for Nextflow Head Instance: The Nextflow head (executor) instance now fully honors your project’s network access policy, just like worker/task instances. When network restrictions are enabled at the project level, both inbound and outbound traffic for the head instance is controlled according to the project’s network settings.

Improvements

  • Right-sized head job resources: Workflows with complex orchestration can now run on more powerful head instances to reduce failures caused by memory issues or controller overload, while lighter workloads can continue using smaller instances to optimize cost.
  • Consistent network policy across compute environments: Project-level network restrictions are now applied consistently to all Nextflow components, including the head instance, ensuring a uniform security posture.
  • Predictable default behavior: When only an app-level head instance is defined, it is used by default. If both app-level and task-level configurations exist, the task-level setting takes priority. Existing apps without head instance configuration will continue to use platform defaults.
  • Clearer UI terminology: The current “Instance type” label for worker tasks has been updated to “Nextflow Worker Instance type” to better distinguish worker resources from head job configuration.

Resources

If you have questions or experience issues, please contact your Velsera Seven Bridges representative or email [email protected].