Multiple input on a node using incorrect input for testing about n8n

[Joffcom]

Hey @pbrink231,

I have taken a look at this and it looks you are seeing the same issue that was reported here: #7509 for the first part.

When the data is pinned it is the same the node will use the data from the path that is triggered from the switch node so in your screenshot the edit fields node is using the pinned data from the High branch as that is the route being taken to trigger the node this doesn't seem like a bug to me and is expected.

If both nodes were to trigger you would see the Run option in the output as the node would run once for each incoming input, This doesn't tell you which node ran to get the data in though so if you wanted to raise a feature request on the community support forum for this we can look at adding it.

For now I believe as this is mostly a duplicate of the other issue I think we can close this, Let me know if I have missed anything or if you have any other concerns and we can open this again.

[pbrink231]

Thank you @Joffcom for taking a look.

I think you pointed out the issue exactly and I looked for previous issues but didn't find that one.

From your response I think I would request 2 features if they don't exist already and hopefully I can try and attack them myself.

• Output, Show which node name the input came from
• Test Step, drop down to choose which input to use
  • workflow (however the flow goes, currently used)
  • input 1
  • input 2
  • etc..

I will put them in later and update here.

[pbrink231]

@Joffcom, There is actually a bug here.

This phase seems to be inaccurate

When the data is pinned it is the same the node will use the data from the path that is triggered from the switch node so in your screenshot the edit fields node is using the pinned data from the High branch as that is the route being taken to trigger the node this doesn't seem like a bug to me and is expected.

It seems the path that is triggered is always the high branch (in the case of pinned data) because it was the first in the input drop down list (explained in the other issue). I believe the "Test step" is not actually using the workflow at all to figure out the input.

I am posting a full detail in the other Issue since it is open and related to this issue.
#7509

[Joffcom]

Hey @pbrink231,

Based on your screenshot and what I spotted that appeared to be the case but it is also very possible that the same issue with first node only being used is in play as well.

[pbrink231]

@Joffcom

I did a test. I removed the "high side" and then added it again. The dropdown input list showing past inputs now had "low side" first, then "high side".

When running the tests everything was reversed. It now used "low side" as the input always instead of "high side".

I don't understand when the nodes are not pinned, why it runs the first time when the workflow is using the first input and then does not work at all after that.