When i run this workflow, “Trigger” is active first (because “Start” is disabled), and then I can see the node “Clickup2” is running, why?
It should have been started if the “Start” node is active, but it is not.
Also, any recommendations for my flow? I’d like “Trigger+Clickup1+Sheets+Merge” to for in prod, and “Start+Clickup2+Sheets+Merge” to run for tests
Hi, thanks for the fast answer. I’ll try to add some details.
Currently, Start is disabled, so i expect the flow to be executed: Trigger+Clickup1+Sheets+Merge
So Clickup2 node should not be executed, when i run the flow manually (with trigger). But it runs for some reason.
Probably because it is back-connected to Merge, but that’s kinda against the flow, literally.
Not sure if Clickup2 was added before or after - but that should not matter, because flow should start with either Start or Trigger and then proceed due to connections, i believe. Otherwise, connections are just not needed, if nodes are executed due to addition time
Yeah, Set+if is something to consider - but that sounds like a workaround. Thanks for the suggestion tho!
PS: i’ve improved the naming a bit, so its Clickup1 and Clickup2 nodes
Yeah. So, my main idea is to set the status for tasks with names listed in spreadsheet.
For prod, i expect Clickup trigger to work. Trigger returns task id.
After the trigger, i get the task details (task name) in Clickup1. After that, i get list of names from the spreadsheet and merge them (that part works fine).
For development, i expect the Start node to execute Clickup2 - it returns list of all tasks (with names). Then i run the spreadsheet node, get the tasks names and merge them.
The idea is that i can swich between dev and prod just by activating the Start/Trigger nodes
Sorry, I didn’t manage to check the video yet. However, from looking at your flow and description I think you’re running into an an oddity of the Merge node here: It essentially pulls data from the other input branch. So in your example when your Google Sheets node runs the Merge node would also cause your ClickUp2 node to run.
I don’t have a great solution for this behaviour unfortunately apart from creating two separate flows (one for production use, one for testing).