The if else node successfully determined that the if/else statement was false, but it did not “activate” the next node that is connected to the else output.
Wasn’t sure how to send a run id, but see the screenshot below that is recognized it as false, but it’s the end of the flow. The supapase - non_leads node should have ran after it, since it has “else response” as an input (in the “Diarized Words” field).
Hey @SimonSays! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
You can find your run history here: https://www.gumloop.com/history
Hey @SimonSays – In order for the subflow Supabase - non_leads to run, all inputs going into the subflow must be present. In this case a few inputs were not present, the ELSE input from the IF-ELSE branch on the Ask AI node is only one of the inputs going into the subflow.
Eg: Thank you Email for Job Application custom node did not run since its connected to the IF branch but the output of this node is being fed as an input of the subflow you would like to run.
In order to solve this you can use the Join Paths node, connect it with both the IF & ELSE branch that way the node runs regardless of the condition upstream. The great part about this setup is that while this node runs regardless of the condition, the subflow will only run when the ELSE condition is met because the Diarized Words input is connected with the ELSE output branch and can only be active when the condition is met.
Let me know if this makes sense and works for you 
That makes sense! Connecting the custom nodes was actually a mistake, so in this case I just disconnected those nodes, and now it works correctly when the else condition is met. But that’s a great solution to keep in mind for future flows.
Thanks so much for your help!
This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.
Awesome! No problem 
