Runtime Cluster v2
Workflows execute on a Cluster. Choose the Cloud Cluster or a registered local Cluster in the Workflow designer.
The whole Workflow runs on that Cluster. Every trigger, ordinary Step, embedded script dependency, and selected Connection must be configured for the same Cluster by choosing it in the Connection Details screen.
A local Cluster can run within your network so Flowgear can interact with resources that are not accessible from the internet. You can restrict a local Cluster to specific Environments. A local Cluster can contain multiple Nodes that operate together, and Flowgear manages load balancing and failover without manual configuration.
When a Workflow invokes a Sub-Workflow, that Sub-Workflow executes according to the Cluster that was specified on it rather than the parent Workflow. This enables Workflows to seamlessly call across Clusters, with full support for lazy evaluation and streaming.
See also
See Local Cluster, Local Clusters Screen, and Local System Integration.