Skip to main content
This page covers task/workflow-level reliability (retry jitter, workflow_timeout, fail_on_callback_error). If you are looking for the gateway-level reliability preset (reliability="production" on BotOS / gateway YAML / CLI), see Gateway Reliability Preset — it is a separate feature that composes drain and admission control.
Make agents survive flaky LLMs, hung workflows, and broken callbacks with built-in retry jitter and configurable failure policies.
This page covers task/workflow reliability (retry, timeouts, failure policies). For gateway reliability (graceful drain + inbound admission control presets), see Gateway Reliability.
The user starts a workflow; retries, timeouts, and failure policies keep flaky LLM or callback errors from aborting the run.

Quick Start

1

Simple Usage

2

With Configuration

Strict mode for CI; lenient mode for production with non-fatal error inspection:

How It Works


Configuration Options

Retry categories

Jitter is automatic — there is no flag to turn it off.

Common Patterns

Strict CI mode

Lenient production mode

Multi-agent fan-out


Best Practices

Network calls can hang indefinitely. Use 60s for quick tasks, 300s for multi-step workflows.
Tests should surface bugs immediately; production should log and continue unless the callback is critical.
The SDK already applies exponential backoff with jitter. Catching RateLimitError and sleeping duplicates that work.
Non-fatal errors indicate latent issues — increment metrics and log them even when the workflow completes.

Task Retry Policy

Per-task retry with exponential backoff

Workflow Error Recovery

Recover from workflow failures gracefully