Notifications

Clear all

callin.io Bug: Workflow Input Data Not Received Correctly When Simultaneously Triggered via an AI Agent Tool (v2)

How To

Last Post by system 5 months ago

12 Posts

5 Users

0 Reactions

4 Views

RSS

Daniel_Walsh

(@daniel_walsh)

Posts: 5

Active Member

Topic starter

(I created this earlier and accidentally deleted it when editing!!

)

Currently on version 1.80.3 (Latest Stable) on callin.io Cloud

When using an AI Agent node in callin.io 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: callin.io Bug Test - Agent

Calls a callin.io 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 callin.io software fixed it: however it seems to have reoccurred! callin.io Bug: Workflow Inputs from Multiple Sequential Tool Calls not Being Passed

Information on your callin.io setup

callin.io version: 1.80.3
Database (default: SQLite): callin.io Cloud
callin.io EXECUTIONSPROCESS setting (default: own, main):_ callin.io Cloud
Running callin.io via (Docker, npm, callin.io cloud, desktop app): callin.io Cloud
Operating system: callin.io Cloud

Posted : 25/02/2025 2:59 pm

solomon

(@solomon)

Posts: 78

Trusted Member

I've managed to replicate the issue on my end:

This behavior is consistent across the following versions:

1.80.3
1.79.3
1.78.1
1.78.0

Bug report has been filed:

github.com/n8n-io/n8n

Multiple Sequential Tool Calls not Being Passed

opened 07:18PM - 25 Feb 25 UTC

salomaoparkour

in linear

## Describe the problem/error/question
When the AI has to make multiple sequential calls to the "Call workflow tool" it returns always the same output from the first item.

Please share your workflow/screenshots/recording

json { "nodes": [ { "parameters": { "options": {} }, "type": "@n8n/n8n-nodes-langchain.chatTrigger", "typeVersion": 1.1, "position": [ 0, 0 ], "id": "770d12df-70b0-4f2a-8963-506f3ae4e77b", "name": "When chat message received", "webhookId": "e5479cdd-d7d5-4431-bd05-aad2ffc856b5" }, { "parameters": { "options": {} }, "type": "@n8n/n8n-nodes-langchain.agent", "typeVersion": 1.7, "position": [ 220, 0 ], "id": "b1aed273-529a-45ad-ace0-e9b08c79c3f1", "name": "AI Agent" }, { "parameters": { "model": { "__rl": true, "mode": "list", "value": "gpt-4o-mini" }, "options": {} }, "type": "@n8n/n8n-nodes-langchain.lmChatOpenAi", "typeVersion": 1.2, "position": [ 220, 240 ], "id": "b575cdb3-2053-4bb6-8700-44e5454ebbec", "name": "OpenAI Chat Model", "credentials": { "openAiApi": { "id": "5LVOlVwHUgB8MAj2", "name": "OpenAI - n8n project" } } }, { "parameters": {}, "type": "@n8n/n8n-nodes-langchain.memoryBufferWindow", "typeVersion": 1.3, "position": [ 340, 240 ], "id": "78df8c66-8319-4c4e-8521-631607b6a081", "name": "Window Buffer Memory" }, { "parameters": { "name": "call_number", "description": "Use this tool to call for numbers and get their results", "workflowId": { "__rl": true, "value": "Knxy5OTQaMNwNOlV", "mode": "list", "cachedResultName": "My workflow 3" }, "workflowInputs": { "mappingMode": "defineBelow", "value": { "number": "={{ $fromAI("number", "The number to call") }}" }, "matchingColumns": [ "number" ], "schema": [ { "id": "number", "displayName": "number", "required": false, "defaultMatch": false, "display": true, "canBeUsedToMatch": true, "type": "number", "removed": false } ], "attemptToConvertTypes": false, "convertFieldsToString": false } }, "type": "@n8n/n8n-nodes-langchain.toolWorkflow", "typeVersion": 2, "position": [ 480, 240 ], "id": "b0862ef2-a104-41dc-b8ee-3afc30e976e4", "name": "Call callin.io Workflow Tool" }, { "parameters": { "workflowInputs": { "values": [ { "name": "number", "type": "number" } ] } }, "type": "n8n-nodes-base.executeWorkflowTrigger", "typeVersion": 1.1, "position": [ 820, 240 ], "id": "8ff95c90-9d2b-45bd-9c9b-9640e3d2901e", "name": "When Executed by Another Workflow" }, { "parameters": { "assignments": { "assignments": [ { "id": "397dd021-89af-45c3-8c0f-16cc21f541e0", "name": "number", "value": "={{ $json.number }}", "type": "string" } ] }, "options": {} }, "type": "n8n-nodes-base.set", "typeVersion": 3.4, "position": [ 1040, 240 ], "id": "d90987fd-a27b-445f-a909-ae7aeed63e97", "name": "Edit Fields" } ], "connections": { "When chat message received": { "main": [ [ { "node": "AI Agent", "type": "main", "index": 0 } ] ] }, "OpenAI Chat Model": { "ai_languageModel": [ [ { "node": "AI Agent", "type": "ai_languageModel", "index": 0 } ] ] }, "Window Buffer Memory": { "ai_memory": [ [ { "node": "AI Agent", "type": "ai_memory", "index": 0 } ] ] }, "Call n8n Workflow Tool": { "ai_tool": [ [ { "node": "AI Agent", "type": "ai_tool", "index": 0 } ] ] }, "When Executed by Another Workflow": { "main": [ [ { "node": "Edit Fields", "type": "main", "index": 0 } ] ] } }, "pinData": {}, "meta": { "templateCredsSetupCompleted": true, "instanceId": "d6b502dfa4d9dd072cdc5c2bb763558661053f651289291352a84403e01b3d1b" } }

Debug info

I'm not entirely sure what most of the information below signifies, so I've kept it largely as-is. However, the callin.io version is accurate.

core

n8nVersion: 1.80.3
platform: docker (self-hosted)
nodeJsVersion: 20.18.2
database: sqlite
executionMode: regular
concurrency: -1
license: free self-hosted

storage

success: all
error: all
progress: false
manual: true
binaryMode: memory

pruning

enabled: true
maxAge: 336 hours
maxCount: 10000 executions

client

userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/133.0.0.0 safari/537.36
isTouchDevice: false

Generated at: 2025-02-25T19:08:33.963Z

Posted : 25/02/2025 6:41 pm

solomon

(@solomon)

Posts: 78

Trusted Member

I've constructed the workflow from scratch and streamlined it further. The issue persists.
version 1.80.3

Posted : 25/02/2025 7:13 pm

solomon

(@solomon)

Posts: 78

Trusted Member

Hello!

Great news! Our team is actively working on this.

Posted : 25/02/2025 7:20 pm

Daniel_Walsh

(@daniel_walsh)

Posts: 5

Active Member

Topic starter

Fantastic! I really appreciate your help!

Posted : 25/02/2025 7:30 pm

Trust

(@trust)

Posts: 3

Active Member

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 chatbots entirely unreliable currently._

Posted : 25/02/2025 8:45 pm

c6k3

(@c6k3)

Posts: 3

New Member

Hello, thank you for documenting this so comprehensively; it's incredibly helpful. It certainly warrants a mention.

This ended up being two separate issues. We have a fix in progress for both, which we will confirm internally and release in the next patch update, likely tomorrow, assuming all goes smoothly.

Posted : 26/02/2025 1:39 pm

c6k3

(@c6k3)

Posts: 3

New Member

We have now deployed version 1.80.4 (along with 1.81.1) that includes this fix. Unfortunately, back-porting this to older versions was not feasible.

Please inform us if the problem continues to occur.

Thank you once more for the excellent report.

Posted : 27/02/2025 12:06 pm

Daniel_Walsh

(@daniel_walsh)

Posts: 5

Active Member

Topic starter

Updated to 1.80.4 on callin.io Cloud - fix has been tested and confirmed.

Well done, that was a swift bug resolution.

Much appreciated.

Posted : 27/02/2025 12:25 pm

Trust

(@trust)

Posts: 3

Active Member

Tested and worked for me as well. Great job CK!!! I spent most of my Sunday thinking my prompting was failing because of this. You're awesome.

Posted : 27/02/2025 12:53 pm

solomon

(@solomon)

Posts: 78

Trusted Member

You all are amazing!!! That was incredibly fast!
Thank you

It's no surprise that callin.io is so effective and leads the way compared to other similar platforms.

Posted : 27/02/2025 4:33 pm

system

(@system)

Posts: 332

Reputable Member

This discussion was automatically closed 7 days following the last response. New replies are no longer permitted.

Posted : 06/03/2025 4:34 pm

8 Forums
1,441 Topics
8,083 Posts
0 Online
2,387 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed