Problems when joining IF branches

Questions
, ,
1

While testing the workflow below, if I click the “balance” node, it doesn’t execute, because it’s waiting for the previous “Create balance” node to execute.

But when executing many nodes at once (for example executing the first node and then executing the “Add transaction” node) it works fine.

It also works fine when running executions, instead of tests.

image
image806×508 31.7 KB

:question::question: My questions are two:

  1. Is this a bug?
  2. Can I have a better approach to this situation, that prevent that kind of behavior during edit?

Information on your n8n setup

  • n8n version: 1.71.3
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Ubuntu 24.04
2

Hey @gmsalomao2

While you wait for an official response, just wanted to add that I’ve also seen the same behaviour many times. I assume when in testing mode, the “balance” node might be checking all inputs are providing data and bails if some don’t.

What I usually do is just temporarily disconnect the inactive incoming branches to continue the flow and reconnect them after I’m done. Not the perfect solution but alternatives? I guess really just doing the verbose way which is making each branch unique rather than shared.

1 Like
3

Thanks for sharing your experience with this issue. I’m also using that workaround.

Guess this is a bug, then?