[BUG] Agentflows v2 Condition not works when 2 or more condition connects same node

[okurayhan]

Agentflows v2 Condition not works when 2 or more condition connects same node.

Please see the screenshot. When I write "hi", Report Value Collection Agent not works. When I duplicate Report Value Collection Agent 5 times and connect all nodes to different agents, it works. But I don't want to duplicate same agents.

[toi500]

I don't think the Condition Node is intended to be used like that (I could be wrong).

The issue is that you're using the Condition Node as if it has multiple OR paths, but it's really an IF/ELSE IF chain. For your use case (for 2 agents), you would to need to combine all your "false" cases into a single condition That way, you only have two outputs: one for True and one for False.

Edit: Also, since you are using the LLM + Condition Node, you could use the Conditional Agent Node directly for a very reliable route.

[okurayhan]

It works in Agentflows v1 version. I want to combine all cases into one node because I am checking every state value is not empty. When all state values are filled another agent will work.

[toi500]

Yeah, I know, in v1 you can also add custom code to the node. Condition Node in V2 is more a simplification of the V1 one, this is why I am unsure if this is a current bug or a limitation.

If what you want is to collect data with one agent first and then to move to the next agent, you also do it like this.

[okurayhan]

First agent collects more than one data. It collects 5 user input value. So I need to run same agent to get 5 value.

[toi500]

Ok...

[guivern]

I am experiencing a similar problem here, in the scenarios where the "LomiBot Orders" agent should be launched, the flow stops

[howardtokka]

same thing happens to my flow it stops at the first node

[iparker]

Same with loop-nodes with input from different nodes:

[LarsEbt]

I'm experiencing the same issue in Flowise version 3.0.5, due to enterprise usage I am unable to update at the moment. Has this been fixed in version 3.0.8?

[marcopixel]

I can also reproduce this, it is very annoying as there is no error logged even with DEBUG enabled... I've made a example flow down below which is currently broken for me (Flowise 3.0.10, self-hosted), i'm suspecting this has maybe to do with passing the same "Flow State" variables to the endnode and then it slipping up somewhere 🤔

Is there any way to help debug this issue? @HenryHengZJ

Agentflow: agent.json