error-recovery-in-langgraph

error-recovery-in-langgraph is a skill for Claude Code, Codex from postindustria-tech/agentic-toolkit. It costs 61 tokens per session (4,053 once invoked), scanned A, original, MIT.

Guidance for handling failures in LangGraph, a Python framework for building step-by-step AI workflows. It covers retries, saved checkpoints, and fallback approaches.

In plain words
What is it for?
Use it when adding retry policies, checkpointing, timeouts, exception handling, or fallback paths to LangGraph workflows.
Why use it?
It helps workflows recover from temporary errors instead of stopping immediately, while preserving state when needed.

Skill for Claude CodeCodex

Part of the langgraph-dev plugin — 21 skills, 4 commands, 1 agent shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery
Any agent
npx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-error-recovery
Clone the repo
git clone --depth 1 https://github.com/postindustria-tech/agentic-toolkit

Made for: Claude Code, Codex.

Or install langgraph-dev, the plugin that ships this one along with the rest of its 21 skills, 4 commands, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for error-recovery-in-langgraph

README.md
[![agentmods](https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery.svg)](https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery)
Your own site
<a href="https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/langgraph-dev-error-recovery.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,053 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.04053
Opus 5 $0.00030 $0.02027
Sonnet 5 $0.00012 $0.00811
Haiku 4.5 $0.00006 $0.00405

Measured 3d ago against content hash 0f0d72f50b2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

error-recovery-in-langgraph scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

# Example: return requests.get(f"https://api.example.com/search?q={query}").text
plugins/langgraph-dev/skills/langgraph-dev-error-recovery/SKILL.md · 540 lines

How it starts

The opening of the file, as written. The whole thing — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error Recovery in LangGraph

Error recovery in LangGraph enables workflows to handle failures gracefully through built-in retry policies, checkpointing for fault tolerance, and custom fallback patterns.

Required Imports

from typing import TypedDict, Optional, Any
from langchain_core.messages import BaseMessage, AIMessage, HumanMessage
from langgraph.graph import StateGraph, START, END
from langgraph.types import RetryPolicy
from langgraph.checkpoint.memory import InMemorySaver
import asyncio
# IMPORTANT: asyncio.timeout requires Python 3.11+
# For Python 3.10: pip install async-timeout && from async_timeout import timeout

LangGraph provides a built-in RetryPolicy for automatic error recovery with exponential backoff and jitter. This is the primary and recommended approach for handling transient failures.

Basic Usage

from typing import TypedDict, Optional, Any
from langgraph.graph import StateGraph, START, END
from langgraph.types import RetryPolicy

class State(TypedDict):
    query: str
    result: Optional[str]
    error: Optional[str]

def api_call_node(state: State) -> dict[str, Any]:
    """Node that calls an external API.

    NOTE: Replace `fetch_from_api` with your actual API client.
    This is a placeholder function for demonstration.
    """
    def fetch_from_api(query: str) -> str:
        """Placeholder for your API client. Replace with actual implementation."""
        # Example: return requests.get(f"https://api.example.com/search?q={query}").text
        return f"Result for: {query}"

    response = fetch_from_api(state["query"])
    return {"result": response, "error": None}

# Create workflow with retry policy
workflow = StateGraph(State)
workflow.add_node(
    "api_call",
    api_call_node,
    retry_policy=RetryPolicy(max_attempts=5)
)
workflow.add_edge(START, "api_call")
workflow.add_edge("api_call", END)

graph = workflow.compile()

RetryPolicy Parameters

Read the full file on GitHub · 540 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 540 lines · 61 tokens per session scan A 0f0d72f50b2e

Subscribe to this mod's changes

error-recovery-in-langgraph is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 4,053 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens