# Parallel Gateway The **Parallel Gateway** is used to split a process flow into **multiple concurrent execution paths**.\ It allows several activities to be executed **at the same time**, without evaluating any conditions. Unlike the **Exclusive Gateway**, which routes the process to only one path based on a condition, the Parallel Gateway always activates **all outgoing paths simultaneously**. *** ### Purpose The **Parallel Gateway** is designed for situations where multiple tasks must be performed **in parallel** as part of a business process. Key characteristics: * All outgoing paths are executed * No condition evaluation is required * Paths run concurrently * Execution continues independently on each branch Parallel Gateways are commonly used when tasks are **independent of each other** and do not require a decision to be made. *** ### Behavior of Parallel Gateway #### Splitting Flow (Fork) When a process reaches a Parallel Gateway with multiple outgoing links: * The process flow is **split into multiple branches** * Each outgoing link is followed * All connected activities start execution at the same time *** #### Synchronizing Flow (Join) A Parallel Gateway can also be used to **synchronize** concurrent paths. In this case: * The gateway waits for **all incoming branches** to complete * Only then does the process proceed to the next activity This ensures that parallel tasks are fully completed before moving forward. *** ### Links and Conditions * Outgoing links from a Parallel Gateway are represented as arrows (`→`) * **No conditions** are defined on these links * All links are always executed when the gateway is reached This makes the Parallel Gateway simpler than Exclusive or Inclusive Gateways in terms of configuration. *** ### Usage Guidelines * Use Parallel Gateway when: * Tasks can run at the same time * No decision logic is required * Do not add conditions to outgoing paths * Ensure that parallel paths are properly synchronized if needed * Clearly structure and label parallel branches for readability * Use a second Parallel Gateway to rejoin parallel flows *** ### Example Use Cases * Send notifications while updating records * Perform multiple validations simultaneously * Execute independent system checks in parallel * Trigger parallel integrations with multiple systems *** ### Summary The **Parallel Gateway** enables **concurrent execution** of tasks within a business process. Key points: * Executes all outgoing paths simultaneously * Does not evaluate conditions * Supports both flow splitting and synchronization * Essential for modeling parallel business activities Using Parallel Gateways correctly allows processes to be **more efficient, expressive, and aligned with real‑world parallel operations** in ONEWEB Process Designer. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.onewebstack.com/oneweb-platform-th/designer-reference/process-designer/process-designer-component/gateway/parallel-gateway.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.