What's new and changed in Orchestration Pipelines

Orchestration Pipelines updates can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic.

You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.

IBM® watsonx™ Version 2.1.3

A new version of Orchestration Pipelines was released in April 2025.

This release includes the following changes:

New features
This release of Orchestration Pipelines includes the following features:
View element details more easily
You can now view detailed information about an element by selecting it in the sidebar. The details are shown in the new Element Information section of the sidebar.
Take advantage of expanded sidebar categories
You can now access enhanced sidebar functionality and more easily navigate by using the new sidebar categories:
  • Loops
  • Node outputs
  • Parameters
  • Parameter sets
  • User variables
Enhanced global object parameters and fields
You can now take advantage of several enhancements when defining and viewing global objects:
  • Parameter set descriptions are now included in the parameter sets table.
  • A new input field, Prompt, is now available for parameters and user variables. This field serves as an optional label with fewer character restrictions than the Name field. When you provide a value for the Prompt, it is used in place of the parameter name while configuring pipeline runs.
  • Under Parameters and User variables, the Description label is now renamed to Help text.
Optimize projects for DataStage
You can use the new Optimized Runner setting to optimize all pipelines at the project level for DataStage use cases. This setting can be configured at the project level and affects all pipelines.
Migrated legacy flows can use this setting to maintain their current settings.
Enhanced flexibility for workflow management
You can now choose how your pipelines save selected jobs from the Run Multiple Jobs node by using the Search by name value or the Exact ID value.
Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak® for Data on the IBM Support website.

IBM watsonx Version 2.1.2

A new version of Orchestration Pipelines was released in March 2025.

This release includes the following changes:

Updates
The following updates were introduced in this release:
  • Tech preview Artifacts, such as metadata files for a pipeline and its child pipelines, are now stored in an embedded database for faster data retrieval. This means that you can now execute large pipeline runs with greater speed.

Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.

IBM watsonx Version 2.1.1

A new version of Orchestration Pipelines was released in February 2025.

This release includes the following changes:

New features
This release of Orchestration Pipelines includes the following features:
Customize how you allocate and use hardware resources by using remote physical locations
Tech preview You can now set up remote physical locations for pipelines. You can customize default hardware specifications and environment variables on the remote physical locations and you can allocate CPU and memory to custom, pipeline-specific environments where you can build your pipeline flows and deployments.
Use Bash script output as node input in a single node
You can now assign your Bash script output as input directly in a node and then run the routine in a single node. With this simplified process, you no longer need to use an extra node to save the Bash script output as a parameter before you use the output as Pipelines node input.

For details, see Configuring pipeline nodes.

Automatically delete associated jobs of a Pipelines asset
You can choose to automatically delete associated jobs when you delete a Pipelines asset in the settings. Any associated jobs for the Pipelines asset are automatically deleted when you delete the asset.

For details, see Manage default settings.

Updates
The following updates were introduced in this release:
  • Bash scripts now have two additional run statuses. If the script completes its run with errors that are handled, the run status is CompletedWithErrors. If the script completes its run with warnings and errors, the run status is CompletedWithWarnings.
  • The Run Bash script node now runs Korn shell scripts in addition to Bash scripts.
Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.
Issues fixed in this release
The following issues were fixed in this release:

IBM watsonx Version 2.1.0

A new version of Orchestration Pipelines was released in December 2024.

This release includes the following changes:

New features
This release of Orchestration Pipelines includes the following features:
Streamline pipeline configuration by specifying settings at the project level

You can now configure pipeline settings at the project level to specify how all assets in the project are created. You can still configure settings, such as autosave, cache, and error policy settings, at the asset level. Any settings that you specify for an individual asset override the project settings.

For details, see Manage default settings.

Simplify job selection by adding multiple jobs to your canvas at the same time

You can now add jobs to pipelines in batch. You can drag the node Run multiple jobs from the node panel onto the canvas, then select one or more job assets, such as the Run DataStage job or the Run Pipelines job. All of the selected assets are added to the canvas with one click.

For details, see Getting started with the Orchestration Pipelines editor.

Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.