Skip to content
Troubleshooting an ...
 
Notifications
Clear all

Troubleshooting an AI Agent Tool called by another AI Agent

6 Posts
3 Users
0 Reactions
3 Views
dmoore44
(@dmoore44)
Posts: 3
Active Member
Topic starter
 

My problem

I have a callin.io workflow with an AI agent that I am setting up to be the primary workflow. It’s triggered by Slack messages, and the AI agent will determine which tool to dispatch the request to.

One of those tools utilizes another AI agent, which is where my issue lies. Ultimately, I’m trying to figure out how I can see what data is being sent to the tool call so that I can configure an “Edit Fields” node that sits between the When Executed by Another Workflow node and the AI agent node.

Please share your workflow

Share the output returned by the last node

The final output from the primary workflow is “workflow completed”, but that’s just filler text. The sub-workflow is failing, and I can’t debug it because I don’t know what inputs are being sent.

Information on your callin.io setup

  • callin.io version: 1.78.1
  • Database (default: SQLite): likely default - it’s locally hosted docker
  • callin.io EXECUTIONS_PROCESS setting (default: own, main): ?
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app): docker
  • Operating system: Docker on Debian
 
Posted : 18/02/2025 4:16 pm
dmoore44
(@dmoore44)
Posts: 3
Active Member
Topic starter
 

Still investigating this, but haven't found a solution yet…

Could someone please offer some guidance?

 
Posted : 21/02/2025 2:25 am
Fraser
(@fraser)
Posts: 5
Active Member
 

When you're editing the second workflow, you should be able to navigate to the Executions tab and view a list of all executions. From there, select one to inspect the data at each node.

Does that assist you?

 
Posted : 23/02/2025 7:07 pm
dmoore44
(@dmoore44)
Posts: 3
Active Member
Topic starter
 

Ah, that does clarify things, thank you! However, I'm now encountering confusion because the secondary workflow isn't receiving a question or prompt. Instead, it's getting a snippet of the original prompt from the main workflow.

 
Posted : 23/02/2025 7:43 pm
Fraser
(@fraser)
Posts: 5
Active Member
 

I suggest reviewing the execution logs to understand the AI's actions.

In your first workflow, navigate to the Executions tab.

Choose the specific Execution run you wish to examine.

Double-click on the AI Agent.

Then, select the Logs tab.

You should observe output similar to this:

This will allow you to see the AI's executed steps, the tools it selects, and the data it passes to the workflow.

Consider enhancing your workflows by providing more details, such as a System Message for the AI Agent, comprehensive information about its available tools, and a clearer definition of its role.

 
Posted : 23/02/2025 11:59 pm
system
(@system)
Posts: 332
Reputable Member
 

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

 
Posted : 24/05/2025 11:59 pm
Share: