-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
A couple use cases:
- On k8s, killing a run leads to the pod/container being destroyed. It can't be "un-killed" later. Sometimes one might want to pause a bunch of runs, e.g. started a big batch of runs, started hitting LLM API rate limits, now want to pause most of them to let some important ones finish, and changing batch concurrency has no effect because the runs are already started.
- this would also mean that pods/nodes stay active and doing nothing, potentially costing us a lot of money
- This could also be used as a mechanism for multi-agent interaction within a task, e.g. by starting multiple branches within the same task and then inserting/removing pauses in e.g. round-robin
Metadata
Metadata
Assignees
Labels
No labels