Quick Start
How It Works
| Setting | Controls | Default |
|---|---|---|
max_iter | Max iterations per task | 10 |
max_retries | Max retries on failure | 5 |
Configuration Options
Full list of options, types, and defaults —
MultiAgentExecutionConfig| Option | Type | Default | Description |
|---|---|---|---|
max_iter | int | 10 | Maximum iterations per task |
max_retries | int | 5 | Maximum retries on task failure |
Common Patterns
Pattern 1 — Long-running research workflow
Pattern 2 — Conservative limits for cost control
Best Practices
Tune max_iter per task complexity
Tune max_iter per task complexity
Simple tasks (classification, extraction) need
max_iter=5–10. Complex research or multi-step synthesis tasks may need max_iter=20–30. Start low and increase if tasks don’t complete.max_retries for fault tolerance
max_retries for fault tolerance
Set
max_retries=3–5 for workflows calling external services that may fail intermittently. For offline or deterministic tasks, max_retries=1–2 is usually enough.Monitor with hooks
Monitor with hooks
Pair
MultiAgentExecutionConfig with MultiAgentHooksConfig to log when retries happen. This helps diagnose why tasks hit their retry limit in production.Related
Multi-Agent Hooks
Intercept task lifecycle events
Multi-Agent Planning
Plan tasks before executing them
Execution Systems
Single-agent execution configuration
Agent Retry
Single-agent retry behavior

