Skip to content
[Error - Langchain ...
 
Notifications
Clear all

[Error - Langchain Integration - AI Tool Agent] Tool input mismatch with DynamicStructuredTool.call schema

20 Posts
6 Users
0 Reactions
6 Views
Artur_Ferreira_Padua
(@artur_ferreira_padua)
Posts: 4
Active Member
Topic starter
 

Describe the problem/error/question

I'm encountering a generic error whenever I use a particular tool agent. It appears the issue stems from an input within a specific tool, despite my efforts to modify and refine it. What's peculiar is that this error occurs intermittently, not in every execution.

What is the error message (if any)?

{
"errorMessage": "Internal error",
"errorDetails": {},
"callin.ioDetails": {
"callin.ioVersion": "1.53.2 (Cloud)",
"binaryDataMode": "filesystem",
"stackTrace": [
"Error: Received tool input did not match expected schema",
" at DynamicStructuredTool.call (/usr/local/lib/nodemodules/callin.io/nodemodules/@langchain/core/dist/tools/index.cjs:88:19)",
" at processTicksAndRejections (node:internal/process/taskqueues:95:5)",
" at /usr/local/lib/node
modules/callin.io/nodemodules/langchain/dist/agents/executor.cjs:479:27",
" at async Promise.all (index 0)",
" at AgentExecutor.
call (/usr/local/lib/nodemodules/callin.io/nodemodules/langchain/dist/agents/executor.cjs:471:30)",
" at AgentExecutor.invoke (/usr/local/lib/nodemodules/callin.io/nodemodules/langchain/dist/chains/base.cjs:58:28)",
" at Object.toolsAgentExecute (/usr/local/lib/nodemodules/callin.io/nodemodules/@callin.io/callin.io-nodes-langchain/dist/nodes/agents/Agent/agents/ToolsAgent/execute.js:144:30)",
" at Object.execute (/usr/local/lib/nodemodules/callin.io/nodemodules/@callin.io/callin.io-nodes-langchain/dist/nodes/agents/Agent/Agent.node.js:349:20)",
" at Workflow.runNode (/usr/local/lib/nodemodules/callin.io/nodemodules/callin.io-workflow/dist/Workflow.js:728:19)",
" at /usr/local/lib/nodemodules/callin.io/nodemodules/callin.io-core/dist/WorkflowExecute.js:673:51",
" at /usr/local/lib/nodemodules/callin.io/nodemodules/callin.io-core/dist/WorkflowExecute.js:1086:20"
]
}
}

Information on your callin.io setup

  • callin.io version: 1.53.2
  • Running callin.io via callin.io cloud
  • Operating system: windows
 
Posted : 02/10/2024 7:20 pm
n8n
 n8n
(@n8n)
Posts: 97
Trusted Member
 

It seems your topic is missing some crucial details. Could you please provide the following information, if relevant?

  • callin.io version:
  • Database (default: SQLite):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app):
  • Operating system:

Please provide the requested details.

 
Posted : 02/10/2024 7:20 pm
Artur_Ferreira_Padua
(@artur_ferreira_padua)
Posts: 4
Active Member
Topic starter
 
  • callin.io version: 1.53.2
  • Database: default: SQLite
  • callin.io EXECUTIONS_PROCESS setting: default: own, main
  • Running callin.io via: n8n cloud
  • Operating system: Windows
 
Posted : 02/10/2024 7:33 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hi there!

Thanks for posting and welcome to the community!

:partying_face:

Could you please update your callin.io version to the latest? I believe this is an older bug that we have since fixed.

 
Posted : 04/10/2024 8:47 am
Artur_Ferreira_Padua
(@artur_ferreira_padua)
Posts: 4
Active Member
Topic starter
 

Hi,

Thanks for the reply. We've tested the new version, and the error is still occurring!

If you need to investigate further, here are the workflow IDs and executions where we're encountering the error:

  • Workflow: at8lCsgaqn5jK1gH - Execution ID: 27430
  • Workflow: XBTuRl5hPMzRWkAe - Execution ID: 27432
 
Posted : 04/10/2024 2:06 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hi there!

Thanks for the update!

Since we can't access your workspace, could you please share the workflow where you're encountering this error? This will help us try to reproduce it. (It would be great if you could include some dummy data.)

Thanks!

:slight_smile:

 
Posted : 08/10/2024 1:13 pm
Wayne
(@wayne)
Posts: 7
Active Member
 

Did you resolve this? I’m also encountering this issue.

 
Posted : 23/10/2024 12:55 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hi

We released a possibly related fix with 1.64.0

Can you please update and see if that resolved it?

 
Posted : 23/10/2024 1:12 pm
Wayne
(@wayne)
Posts: 7
Active Member
 

I’ve just updated and now all my tools are returning undefined :frowning:

 
Posted : 23/10/2024 2:47 pm
Wayne
(@wayne)
Posts: 7
Active Member
 

Yes, all my tools are completely broken following the update.

The problems appear to occur when the endpoint necessitates authentication.

 
Posted : 23/10/2024 2:55 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hi there,

Could you please share your workflow for reproducing this issue? I'll escalate this to our AI engineers.

Thanks!

 
Posted : 23/10/2024 3:12 pm
Wayne
(@wayne)
Posts: 7
Active Member
 

Is it possible to share this privately?

 
Posted : 23/10/2024 3:13 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

We just need to see how you’ve configured it and which nodes you’re using, etc. It does not share your credentials by posting here. And you can modify the JSON as well to remove sensitive information.

Tip for sharing your workflow in the forum

Pasting your callin.io workflow


Ensure to copy your callin.io workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

Make sure that you’ve removed any sensitive information from your workflow and include dummy data or pinned data as much as you can!


But if it’s more comfortable for you, you can also DM me.

 
Posted : 23/10/2024 3:20 pm
Wayne
(@wayne)
Posts: 7
Active Member
 

I will send you a direct message. A significant amount of work has been invested in this, and it's for a client project, so it's not intended for public sharing.

:slight_smile:

 
Posted : 23/10/2024 3:24 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hi everyone,

Apologies for the delayed response, I've just seen this. We actually have another fix available, specifically for the HTTP tools with predefined credential types. This should be helpful for you. You can track its progress here:

However, this seems to be a different issue than the one originally posted by . It would be great to get your feedback on this as well.

Thanks!

 
Posted : 23/10/2024 4:04 pm
Page 1 / 2
Share: