I have an agent who calls up a sub-workflow 5 times in a row. These 5 calls are carried out by the agent in 1 execution. This means that the agent only has 1 execution but the sub-workflow has 5 executions in a row.
Each time the sub-workflow is called from the agent, the agent sends a different query. In the first call, the query is passed on correctly to the sub-workflow. But when the agent calls all the others, the query is not passed on correctly even if the query is different.
The Problem:
The sub-workflow always uses the first query who was send from the agent and ignores all other queries (see attached screenshots).
How can I ensure that the query sent by the agent to the sub-workflow also arrives at the sub-workflow?
Information on your n8n setup
**n8n version: 1.80.3
**Database (default: SQLite): Postgres/Supabase
**n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
This is known bug and other users have reported it too.
This issue has been flagged by n8n team and they are already working on it, since it’s a very problematic bug.
In the meantime, you have a couple of options:
Downgrade to an earlier n8n version that isn’t affected (versions 1.77 or 1.76 should work).
Adjust your workflow by finding an alternative logic using tools instead of sub-workflows.
I know it’s not an ideal solution, but unfortunately, that’s the current situation.
If my reply answers your question, please remember to mark it as a solution.
