Review some best practices when using the Split and merge feature.

Best practices

  • Avoid using elements from other branches as part of variable expressions. You can use elements from the same branch prior to the current node and elements before split node.
  • Avoid deeply nested parallel structures to keep workflows maintainable.
  • Limit the number of parallel tasks to avoid overwhelming runners or systems. However, the system is certified to support up to 10 branches in a split-merge instance.
  • Use parallel splits only for tasks that are truly independent. For example, creating system accounts and allocating hardware are independent and can run parallel. But Validate data and Save validated data cannot run in parallel.
  • Always include a default fallback path for conditional splits.

Known behavior and limitations

  • When you add an If/Else condition inside a branch, an End node is automatically inserted. It is recommended that you delete this End node. Instead, add a Branch Exit node—either from the Elements panel or using the Quick Add option and map your If/Else nodes to the Branch Exit.
  • Currently, the Go to node cannot be used within branches.