--- title: "Cancelling Branch Assignments" slug: "cancelling-branch-assignments-on-denial" description: "Configure a Merge step to cancel pending branch assignments when required conditions are met after parallel Flow execution." updated: 2026-06-08T19:32:13Z published: 2026-06-08T19:32:13Z canonical: "documentation.decisions.com/cancelling-branch-assignments-on-denial" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Cancelling Branch Assignments ## Overview A Merge step can be configured to cancel all other pending branch assignments in a Flow process. The Merge step has the option to factor in certain conditions. For example, if a Split step Branches out to five different Approvals but only requires two, the Merge step will then Cancel the three unworked Tasks that were previously assigned. ## Settings The following example utilizes setting the AllowCancelMerge boolean on the Merge step to cancel an Approval task. The example Forms are arbitrary Approval Forms and could be replaced with a user's specific use case. On the Properties tab of a **Merge** step, select **AllowCancelMerge.** Two Inputs will appear to configure within the Input Properties: **Cancel Pending Forms** and **Cancel Reason**. | **Cancel Pending Forms (Boolean)** | Cancels all pending Assignments that have not yet been satisfied or completed, if set to true. | | --- | --- | | **Cancel Reason (String)** | Stored as a comment within a Process Folder if a Process Folder is being utilized. | There are two options for the Merge Type: **This Flow Only** and **Include Sub-Flows**. | **This Flow Only** | Applies to merges in the current Flow. | | --- | --- | | **Include Sub-Flows** | If Sub-Flows are within the Branch, users may need to set this to **True.** It is important to understand the Scope. For example, there's a flow called Flow A. Flow A contains sub-flow B, and Flow B contains sub-flow C. If a user uses the Include Sub-Flows merge type in Flow B then, it will only merge in sub-flow C. | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1780601947172.png)