Skip to main content
Multi-Agent Execution config controls how many times each task can iterate and how many retries are allowed when tasks fail.
The user sets iteration and retry limits; the workflow stops or retries tasks within those bounds.

Quick Start

1

Simple Usage

2

With Custom Retry Settings


How It Works


Configuration Options

Full list of options, types, and defaults — MultiAgentExecutionConfig

Common Patterns

Pattern 1 — Long-running research workflow

Pattern 2 — Conservative limits for cost control


Best Practices

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.
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.
Pair MultiAgentExecutionConfig with MultiAgentHooksConfig to log when retries happen. This helps diagnose why tasks hit their retry limit in production.

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