Retry and Fallback Paths

Retry and Fallback Paths

Resilience in tool execution.

Retry and Fallback Paths

APIs fail.

The Retry Policy

LangGraph nodes can have retry policies attached.

  • 503 Service Unavailable -> Wait 1s, Retry.
  • 400 Bad Request -> Do NOT Retry. Fail immediately.

The Fallback Edge

If a tool fails permanently:

  • Don't crash.
  • Route to a Fallback Node.
    • Example: Primary Stock API failed? Rout to Backup Stock API.
    • Example: Calculator Tool failed? Ask LLM to estimate (with a warning).

This resilience is defined in the graph edges, keeping your business logic clean.

Subscribe to our newsletter

Get the latest posts delivered right to your inbox.

Subscribe on LinkedIn