Skip to content

[Feature Request] Workforce support replan when decomposed tasks could not be solved #2436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
Wendong-Fan opened this issue May 18, 2025 · 4 comments · May be fixed by #2521
Open
1 of 2 tasks

[Feature Request] Workforce support replan when decomposed tasks could not be solved #2436

Wendong-Fan opened this issue May 18, 2025 · 4 comments · May be fixed by #2521
Assignees
Labels
Agents Related to camel agents system New Feature P0 Task with high level priority
Milestone

Comments

@Wendong-Fan
Copy link
Member

Required prerequisites

Motivation

At the moment, when a decomposed task can’t be handled by the current worker node, the system simply spins up a new agent. We could improve this by adding a task‑replanning mechanism to manage such cases more gracefully

Solution

No response

Alternatives

No response

Additional context

No response

@Wendong-Fan Wendong-Fan added this to the Sprint 30 milestone May 18, 2025
@Wendong-Fan Wendong-Fan added Agents Related to camel agents system New Feature call for contribution P0 Task with high level priority labels May 18, 2025
@zjrwtx zjrwtx self-assigned this May 22, 2025
@zjrwtx
Copy link
Collaborator

zjrwtx commented May 22, 2025

thank @Wendong-Fan ,i will take it

@Wendong-Fan
Copy link
Member Author

To ensure we have a solid design before implementation, an RFC is needed for this feature (Including Problem, Goal, Solution etc). @zjrwtx , would you be able to help prepare this?

@zjrwtx
Copy link
Collaborator

zjrwtx commented May 23, 2025

yeah sure

@zjrwtx
Copy link
Collaborator

zjrwtx commented May 30, 2025

Existing problems :
Lack of task replanning mechanism
If a task fails repeatedly, it may indicate that there are flaws in its decomposition method or execution strategy. Directly creating a new agent is just a "remedy" and does not optimize the task structure at the root.

Failure to utilize existing resources
The system may already have nodes capable of handling the task, but they are not used due to misjudgment by the coordinator.

Lack of failure cause analysis
The specific reasons for failure (such as model limitations, lack of tools, logical errors, etc.) are not recorded, making it impossible to develop a more targeted recovery strategy.

The task nesting depth threshold is fixed get_depth() >= 3 is a hard - coded judgment condition and cannot adapt to all task types.

Task Replanning Module that:

Analyzes the reason for failure
Adjusts the task description or goal
Makes smarter decisions on whether to rewrite,retry, decompose, or create a new worker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agents Related to camel agents system New Feature P0 Task with high level priority
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants