Skip to main content
Hierarchical workflows automatically handle common failure modes with built-in retry mechanisms and intelligent error recovery.
The user starts a hierarchical team run; retries and manager re-prompts recover parse and assignment errors automatically.

Quick Start

1

Create Hierarchical Workflow

2

Start Workflow


How It Works


Configuration Options

These constants are not user-configurable today; they are SDK defaults designed for optimal reliability. Future versions may expose configuration options.

Error Recovery Types

Parse Failures

When: Manager LLM returns invalid JSON Recovery: Retry with exponential backoff Max: 3 attempts before abort

Invalid Task IDs

When: Manager selects non-existent task Recovery: Re-prompt with valid ID list Max: 3 attempts before abort

Loop File Errors

When: Cannot read loop input file Recovery: Mark task as failed with error Visibility: Error shown in TaskOutput

Best Practices

Isolate errors in parallel and loop steps so one failure does not abort unrelated work.
Return structured error details agents and UIs can display instead of silent exceptions.
Use before/after hooks to retry, notify, or escalate when steps fail.
Verify missing input files produce clear TaskOutput messages before production runs.

Hierarchical Workflows

Manager-based validation and graceful failure handling

Hooks

Custom error handling with hooks