How to continue workflow after output?
I tried this approach: https://support.buildship.com/m/1261169034783756332
1. Parallel Execution Node: Add a Parallel Execution node to your workflow. This node will allow you to run multiple branches in parallel.
2. Branch 1 - Return Node: In the first branch, add your Return node to send the response back to the client.
3. Branch 2 - Airtable Node: In the second branch, add your Airtable nodes to check if the user exists and update or create the user accordingly.
4. Continue Workflow: After the Airtable nodes, you can add more nodes to continue your backend tasks.
And it didn't work.
What my workflow did is that it only execute the first node in branch 2 and immediately terminates.
Is this a bug?
How to Continue Workflow After a Return Node - BuildShip
In BuildShip, the
Return node is typically used to terminate the workflow and send a response back to the client. If you need to continue the workflow after sending a response, you can use the Parallel Execution node to run multiple flows concurrently.
Here's a step-by-step guide on how you can achieve this:
1. Parallel Execution Node:...2 Replies
AI Support Bot Information
<@526789266878103570> 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
The issue you're experiencing with the Parallel Execution Node, where it only executes the first node in branch 2 and terminates, could be due to the configuration of the branches or the nodes involved in the workflow. Here are some steps to debug and possibly resolve the issue:
1. Branch Node Configuration: Ensure that the branch node is correctly configured. The branch node should be using the correct conditions to route the workflow to the appropriate branches.
2. Airtable Node Execution: Check the Airtable node's configurations and ensure that they are set up correctly to query and update data as expected. If there's an error in the Airtable node, it might cause the workflow to terminate prematurely.
3. Error Handling: Implement error handling for the nodes within the branches. This will help identify if there’s a specific error causing the workflow to halt.
4. Workflow Logs: Review the workflow logs to identify any errors or warnings that occurred during execution, which can provide insights into why the workflow stopped unexpectedly.
5. Node Dependencies: Check if there are any dependencies or conditions required for the nodes in branch 2 to execute successfully.
If the issue persists after checking these aspects, you might need to reach out to BuildShip support for further assistance or consider sending a support request via in-app support.
BuildShip AI Support