Published at: 2026-09-17

Configure parallel gateway nodes


Send multiple parallel branches at the same time.

Overview

A Parallel Gateway node sends tasks to multiple next-step nodes or approvers at the same time. Each parallel branch is handled independently and is not affected by other branches.

Before you begin

  • The Approval Process is created.
  • You have identified the parallel branches.
  • You have identified the processing node for each branch.

Configuration steps

  1. In the process designer, add Parallel Gateway.
  2. In Node Settings on the right, enter Node Name. For example, enter Functional department collaboration.
  3. Enter Node Description as needed.
  4. Connect the Parallel Gateway to multiple subsequent nodes, such as commercial owner, legal owner, and finance owner.
  5. Configure each subsequent node separately.
  6. Check whether all branches can merge or end.
  7. Click Save.
Configure Parallel Gateway
A Parallel Gateway mainly controls branch relationships. Each subsequent branch still requires a specific Approval Node, Collab Node, or other node configuration.

Configure rejection routing

A Parallel Gateway supports rejection routing configuration:
  • Reject to a non-gateway node, then jump back to the original node after handling: After a branch is rejected, it jumps to a specified node. After handling is complete, it returns to the original node and continues.
  • Reject and end the process, then jump back to the original node after resubmission: After a branch is rejected, the current process ends. After resubmission, it returns to the original node.
Choose whether to enable rejection routing based on business rules. This prevents parallel branches from being unable to return to the correct node after rejection.

Configuration recommendations

  • Keep responsibilities clear for parallel branches.
  • Avoid having multiple branches update the same field at the same time.
  • Configure clear assignees and timeout reminders for each branch.
  • Verify the routing result after all branches are completed.

Expected result and verification

  1. Use a test record to trigger the process.
  2. Check whether tasks for multiple branches are generated at the same time.
  3. Complete tasks in each branch.
  4. Check whether the process continues as expected.

Related topics

Submit Feedback