The Use of Two FunctionCallingAgents Within a Single Workflow
The Use of Two FunctionCallingAgents Within a Single Workflow
At a glance
A community member has a question about using two FunctionCallingAgents within a single workflow. They have created an Agent A that decides which event to execute (Event A or Event B), and Event B utilizes another FunctionCallingAgent. The community member is unsure if this approach is valid and is experiencing issues with the implementation. They are looking for guidance and relevant resources or examples on how to implement a multi-agent system within a workflow, where Agent A interacts with Agent B.
The comments suggest that the issue is likely with the implementation, and the community members are requesting more information, such as code examples, to provide further opinions. One community member has resolved the issue and expressed confidence in the approach.
Hello @Logan M , @WhiteFang_Jr , @ravitheja , @Seldo .
I have a question regarding the use of two FunctionCallingAgents within a single workflow ?
Here's the scenario: I’ve created Agent A, which decides which event to execute (Event A or Event B). Now, Event B utilizes another FunctionCallingAgent. Is this approach valid?
I’ve attempted this setup, but it’s not functioning as expected. I’d like to confirm whether this is a feasible implementation or if adjustments are needed.
My aim to implement a multi-agent system within a workflow, where Agent A interacts with Agent B. Could you share any relevant resources or examples to guide me on this?
Event B works as expected when I don't declare an Agent initially. However, when the Agent is declared first, I'm not getting the expected response.
What could be the reason for this? If you have any examples or resources related to scenarios where Agent A interacts with Agent B using workflows, please share them.
