N8N Bug: Workflow Input Data Not Being Received Correctly When Simultaneously Triggered via an AI Agent Tool (v2)

(I created this earlier and accidently deleted it when editing!! :rofl:)

Currently on version 1.80.3 (Latest Stable) on N8N Cloud

When using an AI Agent node in n8n to simultaneously trigger another workflow (via the “Execute Workflow” node), the input data provided to the workflow is not being received correctly by the triggered workflow.

In my test use case, I’m asking the AI Agent to trigger the workflow 3 times simultaneously.

In the first call, pass the number 1
In the second call, pass the number 2
In the third call, pass the number 3

The workflow being called simply responds with the number it receives

When tested, each call responds with the number 1 - which is obviously incorrect.

The problem doesn’t occur if there are single sequential tool calls (with multiple LLM calls in between tool calls).

Setup:

WORKFLOW 1: N8N Bug Test - Agent

Calls an N8N workflow multiple times using the Execute Workflow tool simultaneously.

System Prompt

“This is a test.
No matter the user prompt, you must do the following …
STEP 1. AT THE SAME TIME … Call “workflow” and pass the number 1 AND Call “workflow” and pass the number 2 AND Call “workflow” and pass the number 3
Output the results”

WORKFLOW 2 - Receiving Workflow

Contains only:
“When Executed by Another Workflow” trigger node (with a message (string) input)


A basic Code node that returns the data it receives directly.

I encountered this issue before, and an upgrade to the N8N software fixed it: however it seems to have reoccured! N8N Bug: Workflow Inputs from Multiple Sequential Tool Calls not Being Passed

Information on your n8n setup

  • n8n version: 1.80.3
  • Database (default: SQLite): N8N Cloud
  • n8n EXECUTIONS_PROCESS setting (default: own, main): N8N Cloud
  • Running n8n via (Docker, npm, n8n cloud, desktop app): N8N Cloud
  • Operating system: N8N Cloud
4 Likes

I was able to reproduce the bug on my end:

All these versions have the same behavior:

  • 1.80.3
  • 1.79.3
  • 1.78.1
  • 1.78.0

@Jon and @c6k3 can you give us hand?

Bug report created:

2 Likes

I’ve built the workflow from scratch and made it even simpler. Same problem.
version 1.80.3

Hey, @Daniel_Walsh

Good news! The team is already working on it :muscle:

Epic!!! Really appreciate it!

1 Like

Kudos to both of you for documenting better than me.

FYI - every ticket gets set for tracking automatically until review (this is automated).

I reported in #13453

This is a major hair on fire issue, that makes ai chat bots entirely unreliable currently.

2 Likes

Hey, thanks for documenting this thoroughly, it’s a huge help. Also definitely justifies a ping :sweat_smile:

This actually turned out to be two issues, we have a fix incoming for both which we’ll verify internally and deploy with the next patch release, most likely tomorrow, if everything goes well.

3 Likes

We now deployed 1.80.4 (and 1.81.1) with this fix.
A back-port to older versions unfortunately was not viable.

Please let me know if the issue persists.

Thanks again for the great report :raised_hands:

2 Likes

Upgraded to 1.80.4 on N8N Cloud - fix tested and verified

Fair play, that was a fast bug fix.

Appreciate it

2 Likes

Tested and worked for me also. Great job CK!!! I burned most of my Sunday thinking my prompting was failing because of this. You f***ing rock.

1 Like

You guys rock!!! That was super fast!
Thank you :raised_hands::raised_hands:

No wonder n8n is so good and ahead of other similar solutions.

1 Like

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