Create new branch from existing workflow
How do i create a separate branch of nodes that starts at the middle of an existing workflow? When I try to create a new branch, the new branch automatically terminates at the old branch. I want to create a separate path, not redirect back to the parent path. Image attached of what I'm trying to do.
Thanks for the help.
Solution:Jump to solution
@Stacker You can clone this workflow it is built on to of your shared workflow to showcase how you can add a separate branch from the middle of your workflow - (shared via email) Also please note that the Output/Return node acts as the ending point of your workflow adding any node below it won't execute.
4 Replies
AI Support Bot Information
<@394761776379461632> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
To create a separate branch of nodes that starts in the middle of an existing workflow without it terminating at the old branch, follow these steps:
1. Identify the Node: Locate the node from which you want to create the separate branch in your existing workflow.
2. Branching/Parallel Execution: Use a "Parallel Execution" or "Branching" node, if available, after the identified node. This node allows you to branch out into separate paths from a single node. The parallel execution node processes each branch independently.
3. Configure Output Connections: Once you have placed the Parallel Execution node, make sure to connect the output of the earlier node to this new node. Then, connect each branch path from the Parallel Execution node to the following nodes you wish to include in each path.
4. Ensure Endpoints for Each Path: Make sure that each separate path has its own endpoint or termination condition, meaning that it can run completely independently of the other paths.
By doing this, you will effectively create a separate branch that runs concurrently or separately from other branches, depending on the configuration of your parallel execution or branching node.
If specific node functionalities or terminologies like "Parallel Execution" aren't matching with what you're using, it might be helpful to check your BuildShip documentation or tools for the exact name and functionality of the node that allows branching or parallel processing. If your image illustrates something specific or unique in your setup, consider reviewing it for any particular adjustments that might be needed.
For more specific guidance, you can refer to the BuildShip documentation on workflows and node connections here.
BuildShip AI Support
This method doesn't solve my problem. If I have a series of nodes that look like this: A -> B -> C, but I want it to be A -> B -> C or A -> B2 -> D (depending on a condition in A), creating a parallel execution or branching node just creates A -> A2/A3/A4 -> B -> C (there is no true separate branch).
Solution
@Stacker You can clone this workflow it is built on to of your shared workflow to showcase how you can add a separate branch from the middle of your workflow - (shared via email) Also please note that the Output/Return node acts as the ending point of your workflow adding any node below it won't execute.