Sub-workflow trigger has different inputs than "execute workflow" node

Questions
1

Describe the problem/error/question

Hey, I’m having problems with the “Execute sub-workflow” node as well as the Trigger of the sub-workflow. I’m passing on a string value called “richting”, which can either be “stadteinwärts” or “stadtauswärts”. However, in the execution of the sub-workflow, it always reverts to “stadteinwärts”. I’m very confused. Already restarted and updated n8n, but it still happens.

Please share your workflow

image
image502×824 24.5 KB

image
image979×593 23 KB

Information on your n8n setup

  • n8n version: 2.8.3
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker Compose
  • Operating system: Linux
2

Hey @tom.jdg Welcome back to the n8n community!

Can you please share a bit of your workflow so that i can assist you better as this issue is quite unusual

1 Like
3

Hey, thanks for your reply! I can’t share really much of the workflow as almost every node includes some info to where I live :sweat_smile:

I did some more testing and found out, the “richtung”:”stadteinwärts” field was like frozen. Even if I removed it from the inputs (in both the main workflow, and the expected inputs), it still appeared with the other fields.

Copy/pasting the nodes into a new workflow did nothing, the final fix was to re-create the workflows from scratch, node after node, and only copy/pasting the node parameters if required. Now everything works as expected.

If the devs would like the old workflows to investigate the issue, feel free to contact me, otherwise I think this is solved :slightly_smiling_face::+1:

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.