crewAI icon indicating copy to clipboard operation
crewAI copied to clipboard

[FEATURE] Iterative implementation in tasks due to inconsistent delegation when working with smaller LLM

Open CommiAI opened this issue 1 year ago • 1 comments

Feature Area

Task management

Is your feature request related to a an existing bug? Please link it here.

I tried to implement a crew that contains a data analysis agent and an SQL data fetching agent, with the SQL data fetching agent having the tool to connect to my database. The idea was to let the data analysis agent first look at initial data and spot any anomalies, suspect a root cause, and then iteratively investigate for the root cause through request more data from SQL data fetching agent and analysis the newly fetched data. I built it as hierarchical process but encountered problem when manager agent keep delegating wrong task to the wrong agent, or just pass repeated task to the same agent. My thought is to implement with two task, data fetching and data analyzing, with conditional task, but it seems that conditional task only check sequentially, meaning if I do data analyze -> need more data -> fulfill conditional task condition -> fetch more data -> can't return back to data analyze task. image

Describe the solution you'd like

Implementation of iterating tasks such as routing for tasks, or spawn tasks sets: x amount of tasks combination based on config

Describe alternatives you've considered

No response

Additional context

No response

Willingness to Contribute

I can test the feature once it's implemented

CommiAI avatar Dec 18 '24 07:12 CommiAI

So , I also have. small doubt in this process , are you able to send the result from one task to another as it is important in this situation or are you logging them into some file and checking from that?

Faced similar issues , where allow_delegation is not working as intended and waste of so much tokens.

naredlarohithreddy avatar Jan 04 '25 17:01 naredlarohithreddy

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Feb 04 '25 12:02 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

github-actions[bot] avatar Feb 10 '25 12:02 github-actions[bot]