Node behavior: Repeated tool calls with identical arguments

Hi, we've implemented some fixes for similar issues in version 1.67.

Could you please upgrade and verify if you're still encountering the same problem? If the issue persists, we will prioritize investigating it further.

Hi David,

Thanks for the quick reply!

No, I’m on the latest release 1.66. I’ll test it with 1.67 when released and let you know.
In the mean time, I’ve used a “call callin.io workflow tool” and it works well.

Hi,
I've just updated my version and re-ran my workflow, encountering a similar issue.

The agent has 7 input items.

The Notion "create insight" node is called only once during the entire execution, according to the logs.

The input contains just one element, which is expected since the agent only needs to create one insight.

image1196×470 20 KB

However, it's creating 7 entries in my Notion database. The output shows 7 elements, as if the tool was called for each input item, rather than just the single one.

image1180×1090 95.7 KB

image558×720 26.9 KB

Thanks for your continued investigation.

We've pinpointed the problem and are actively developing a solution. While you've already discovered a temporary fix, an alternative approach involves nesting the agent within a loop, ensuring it processes only one item at a time.

Thank you!

Currently, I'm utilizing a sub-workflow to generate the insight. That's a fantastic aspect of having various approaches available.

For your information: I've re-tested it with the most recent version, and the issue persists.

Hi everyone,
I'm also encountering a similar problem.
I have a MySQL Tool node linked to a Tools AI Agent, which runs queries generated by the agent.
When this tool is called repeatedly, it only executes the initial query.
The logs indicate the second query is being sent, but the backend is still running the first one.

Please provide some guidance on this issue.

You're likely aware of this by now...

I've also experimented with the Airtable node tool "delete record," and it exhibits the same behavior: it only deletes the first record (identified by another Airtable node tool, "search records").

The same workaround applies; I'm using an HTTP request instead, which functions perfectly.

Thanks for the additional context. We are actively working on a solution for this issue and anticipate having it available shortly.

Hi, it’s the same with nocoDB for create, delete, and with Google calendar.
Thanks

I'm encountering the same issue. I managed to resolve it using the HTTP request Tool. I'm facing a similar problem with the Supabase Tool. I'm eager to find a solution for this, as it would simplify things considerably.

Just wanted to mention that I'm encountering the same problem with the Google Calendar tool.

Primarily posting this to be notified when the fix is released.

Thanks to the callin.io developers for all your hard work!

callin.io is an AMAZING tool!

First off: +1 to the original poster! I completely agree that this is an amazing tool, the community is fantastic, and I'm incredibly impressed with the development work the team is doing!

I wanted to highlight another issue I've encountered with the Airtable node as a tool.
I'm uncertain if it's directly related to the bug mentioned, so please advise if I should start a separate thread.

When my agent invokes the same tool multiple times with different parameters, it seems to return the same object as the initial call. Initially, I suspected a visual bug, but upon inspecting the chat model logs, I observed that this behavior is also being passed to the LLM.

Context:
I'm using an Airtable node configured as a tool to search through Airtable records.

Example (this is a search by keyword, returning items that contain the word in their Description field):

image824×286 27.8 KB

When the agent queries the tool, it appears to be using different parameters, but I suspect it is not.

image1518×856 71.7 KB

image1596×930 77.7 KB

You can observe in this last screenshot that the description does not contain the word "efficiency", but it does contain the word "productivity" (from the first call's parameters). I've just verified, and my Airtable table does have other records with the word "efficiency" in the Description field, so it should be returning different results.

Finally, you can see in this log that the chat model node is receiving the same response from the agent three times.

image1728×1560 317 KB

My apologies for the lengthy message; I hope this explanation is clear.

Any updates on this matter?

I've run into a comparable problem. Has there been any recent advancement?