Langchain  

Custom Error Hierarchies in Enterprise LangGraph Multi-Agent Systems

In enterprise AI deployments, a generic try...except Exception block is a death sentence for production reliability. When a Multi-Agent LangGraph system fails, the system doesn't just need to know that it failed; it needs to know why it failed to determine how to recover. A missing field in a PDF requires user intervention. A 500 error from a third-party API requires an exponential backoff retry. An LLM inference timeout requires a fallback to a smaller, faster model. Treating all these failures identically leads to infinite retry loops, wasted compute, and frustrated users. In this end-to-end guide, we will design a Custom Python Error Hierarchy and integrate it into an Enterprise Multi-Agent LangGraph RAG System with persistent memory. We will build a Real-Time Financial Compliance Agent that catches specific errors, updates the graph state, and autonomously routes to self-healing recovery nodes.

The Real-World Use Case: Real-Time Financial Compliance Monitoring

Imagine an enterprise system monitoring incoming financial documents (earnings calls, 10-K filings) in real-time to check for regulatory compliance and market anomalies.

The Pipeline:

  1. Ingestion & Validation: Extract text and validate the presence of a valid Stock Ticker.

  2. Market Data Fetching: Query a real-time external API (e.g., Bloomberg/SEC) for current market cap and peer data.

  3. RAG & LLM Analysis: Retrieve compliance rules from a Vector DB and use an LLM to analyze the document against the rules.

The Failure Modes:

  • Data Validation Error: The uploaded document is an image-only PDF or lacks a ticker symbol. Action: Halt pipeline, notify user.

  • API Failure: The external market data API is rate-limited or down. Action: Retry with exponential backoff up to 3 times.

  • Inference Timeout: The document is 100 pages long, and the primary LLM (gpt-4o) exceeds the 30-second SLA. Action: Fallback to a faster model (gpt-4o-mini) or chunk the document.

5001

Designing the Custom Error Hierarchy

We create a structured exception tree. This allows us to catch broad categories of errors (e.g., AgentBaseError) or highly specific ones (e.g., InferenceTimeoutError).

# src/exceptions.py

class AgentBaseError(Exception):
    """Base exception for all enterprise agent errors."""
    def __init__(self, message: str, context: dict = None):
        super().__init__(message)
        self.message = message
        self.context = context or {}

# --- 1. Data Validation Errors ---
class DataValidationError(AgentBaseError):
    """Raised when input data is malformed or missing required fields."""
    pass

class MissingTickerError(DataValidationError):
    """Specific validation error for missing stock tickers."""
    pass

# --- 2. External API Errors ---
class ExternalAPIError(AgentBaseError):
    """Raised when an external service (DB, API, Vector Store) fails."""
    pass

class MarketDataAPIError(ExternalAPIError):
    """Specific error for the financial market data provider."""
    pass

# --- 3. Model Inference Errors ---
class InferenceError(AgentBaseError):
    """Raised when the LLM fails to generate a response."""
    pass

class InferenceTimeoutError(InferenceError):
    """Raised when the LLM exceeds the maximum allowed execution time."""
    pass

Architecture Overview: State-Driven Error Recovery

In standard Python, an unhandled exception crashes the thread. In LangGraph, we intercept these custom errors, write them to the Graph State, and use Conditional Edges to route the execution to specialized recovery nodes.

[ Incoming Document ]
          │
          ▼
┌───────────────────────┐
│ 1. Validate Document  │ ──(DataValidationError)──> [ Alert User Node ]
└───────────┬───────────┘
            │ (Success)
            ▼
┌───────────────────────┐
│ 2. Fetch Market Data  │ ──(ExternalAPIError)───> [ Retry Node ] ──┐
└───────────┬───────────┘                                               │
            │ (Success)                                                 │ (Retries < 3)
            ▼                                                           │
┌───────────────────────┐                                               │
│ 3. RAG LLM Analysis   │ ──(InferenceTimeoutError)──> [ Fallback Node ]
└───────────┬───────────┘
            │ (Success)
            ▼
      [ Final Report ]

End-to-End Python Implementation

Prerequisites

pip install langgraph langchain-openai langchain-core

Step 1: Define the LangGraph State and Memory

The state must include fields to track errors and retry attempts. We use MemorySaver to persist this state across conversational turns.

from typing import TypedDict, List, Dict, Any, Optional
from langgraph.checkpoint.memory import MemorySaver

class ComplianceState(TypedDict):
    document_text: str
    ticker: Optional[str]
    market_data: Optional[Dict[str, Any]]
    compliance_rules: str
    final_analysis: str
    
    # Error Tracking & Recovery State
    error_type: Optional[str]
    error_message: Optional[str]
    api_retry_count: int
    use_fallback_model: bool

Step 2: The Multi-Agent Nodes (with Custom Error Handling)

Each node performs its task. If it encounters a failure, it catches the specific custom exception, updates the state with the error details, and returns.

import asyncio
import random
from src.exceptions import (
    MissingTickerError, MarketDataAPIError, InferenceTimeoutError
)

# --- Node 1: Validation ---
def validate_document_node(state: ComplianceState) -> Dict[str, Any]:
    """Validates the document. Raises custom error if invalid."""
    text = state.get("document_text", "")
    
    # Simulate extracting a ticker
    if "TICKER:" in text:
        ticker = text.split("TICKER:")[1].strip().split()[0]
    else:
        # Catching our own custom error to update state instead of crashing the graph
        try:
            raise MissingTickerError("Document does not contain a valid TICKER identifier.")
        except MissingTickerError as e:
            return {
                "error_type": "validation",
                "error_message": e.message,
                "ticker": None
            }
            
    return {"ticker": ticker, "error_type": None, "error_message": None}

# --- Node 2: Market Data API ---
async def fetch_market_data_node(state: ComplianceState) -> Dict[str, Any]:
    """Fetches external data. Simulates API failures."""
    retry_count = state.get("api_retry_count", 0)
    
    # Simulate a flaky API (fails 50% of the time)
    if random.random() < 0.5:
        try:
            raise MarketDataAPIError("Upstream provider returned HTTP 503", context={"retry": retry_count})
        except MarketDataAPIError as e:
            return {
                "error_type": "api_failure",
                "error_message": e.message,
                "api_retry_count": retry_count + 1,
                "market_data": None
            }
            
    # Success scenario
    return {
        "market_data": {"market_cap": "50B", "sector": "Tech"},
        "error_type": None,
        "error_message": None
    }

# --- Node 3: RAG LLM Analysis ---
async def rag_analysis_node(state: ComplianceState) -> Dict[str, Any]:
    """Runs RAG and LLM inference. Simulates timeouts."""
    use_fallback = state.get("use_fallback_model", False)
    
    # Simulate a timeout if not using the fallback model
    if not use_fallback:
        try:
            # Simulate a 40-second LLM call
            await asyncio.sleep(40) 
            raise InferenceTimeoutError("LLM inference exceeded 30s SLA.")
        except InferenceTimeoutError as e:
            return {
                "error_type": "inference_timeout",
                "error_message": e.message,
                "final_analysis": None
            }
            
    # Success scenario (Fallback model is fast)
    return {
        "final_analysis": "Document complies with SEC regulations. Market data aligns.",
        "error_type": None,
        "error_message": None
    }

Step 3: The Recovery & Routing Nodes

These nodes read the error_type from the state and execute the specific recovery strategy.

def handle_validation_error_node(state: ComplianceState) -> Dict[str, Any]:
    """Terminal node for validation errors. Escalates to human/user."""
    print(f" VALIDATION ESCALATION: {state['error_message']}")
    return {"final_analysis": f"HALTED: {state['error_message']}"}

async def handle_api_retry_node(state: ComplianceState) -> Dict[str, Any]:
    """Retries the API call with exponential backoff."""
    retry_count = state["api_retry_count"]
    wait_time = 2 ** retry_count
    print(f" API RETRY {retry_count}/3: Waiting {wait_time}s...")
    await asyncio.sleep(wait_time) # Simulate backoff
    
    # Clear error state to allow the graph to route back to the API node
    return {"error_type": None, "error_message": None}

async def handle_inference_fallback_node(state: ComplianceState) -> Dict[str, Any]:
    """Switches to a faster, cheaper model to avoid timeout."""
    print(" INFERENCE FALLBACK: Switching to gpt-4o-mini...")
    return {"use_fallback_model": True, "error_type": None, "error_message": None}

Step 4: Routing Logic and Graph Compilation

We define the conditional edges that inspect the state and route to the correct recovery node.

from langgraph.graph import StateGraph, START, END

def route_after_validation(state: ComplianceState) -> str:
    if state.get("error_type") == "validation":
        return "handle_validation"
    return "fetch_market_data"

def route_after_api(state: ComplianceState) -> str:
    if state.get("error_type") == "api_failure":
        if state["api_retry_count"] >= 3:
            return "handle_api_max_retries" # Give up
        return "handle_api_retry" # Retry
    return "rag_analysis"

def route_after_rag(state: ComplianceState) -> str:
    if state.get("error_type") == "inference_timeout":
        return "handle_inference_fallback"
    return "finalize"

def handle_api_max_retries_node(state: ComplianceState) -> Dict[str, Any]:
    print(" API MAX RETRIES EXCEEDED. Halting pipeline.")
    return {"final_analysis": "HALTED: External API unavailable after 3 retries."}

def finalize_node(state: ComplianceState) -> Dict[str, Any]:
    return {"final_analysis": state["final_analysis"]}

# Build the Graph
def build_compliance_graph():
    workflow = StateGraph(ComplianceState)
    
    # Add Nodes
    workflow.add_node("validate", validate_document_node)
    workflow.add_node("fetch_market_data", fetch_market_data_node)
    workflow.add_node("rag_analysis", rag_analysis_node)
    
    # Add Recovery Nodes
    workflow.add_node("handle_validation", handle_validation_error_node)
    workflow.add_node("handle_api_retry", handle_api_retry_node)
    workflow.add_node("handle_api_max_retries", handle_api_max_retries_node)
    workflow.add_node("handle_inference_fallback", handle_inference_fallback_node)
    workflow.add_node("finalize", finalize_node)
    
    # Define Edges
    workflow.add_edge(START, "validate")
    
    workflow.add_conditional_edges(
        "validate", 
        route_after_validation,
        {
            "handle_validation": "handle_validation",
            "fetch_market_data": "fetch_market_data"
        }
    )
    
    workflow.add_conditional_edges(
        "fetch_market_data",
        route_after_api,
        {
            "handle_api_retry": "handle_api_retry",
            "handle_api_max_retries": "handle_api_max_retries",
            "rag_analysis": "rag_analysis"
        }
    )
    
    # Route API retry back to the API node
    workflow.add_edge("handle_api_retry", "fetch_market_data")
    
    workflow.add_conditional_edges(
        "rag_analysis",
        route_after_rag,
        {
            "handle_inference_fallback": "handle_inference_fallback",
            "finalize": "finalize"
        }
    )
    
    # Route inference fallback back to the RAG node
    workflow.add_edge("handle_inference_fallback", "rag_analysis")
    
    workflow.add_edge("handle_validation", END)
    workflow.add_edge("handle_api_max_retries", END)
    workflow.add_edge("finalize", END)
    
    # Compile with Memory
    memory = MemorySaver()
    return workflow.compile(checkpointer=memory)

app = build_compliance_graph()

Step 5: Execution and Simulation

Let's simulate a real-time stream of documents to see how the custom error hierarchy drives the graph's self-healing behavior.

import uuid

async def run_compliance_stream():
    thread_id = str(uuid.uuid4())
    config = {"configurable": {"thread_id": thread_id}}
    
    print("--- Scenario 1: Missing Ticker (Validation Error) ---")
    state_1 = {
        "document_text": "Q3 Earnings Report. Revenue is up 20%.", # No TICKER:
        "ticker": None, "market_data": None, "compliance_rules": "", 
        "final_analysis": "", "error_type": None, "error_message": None, 
        "api_retry_count": 0, "use_fallback_model": False
    }
    await app.ainvoke(state_1, config)
    
    print("\n--- Scenario 2: Flaky API & LLM Timeout (Auto-Recovery) ---")
    state_2 = {
        "document_text": "Q3 Earnings Report. TICKER: AAPL. Revenue is up 20%.",
        "ticker": None, "market_data": None, "compliance_rules": "", 
        "final_analysis": "", "error_type": None, "error_message": None, 
        "api_retry_count": 0, "use_fallback_model": False
    }
    
    # Stream the events to watch the self-healing in real-time
    async for event in app.astream(state_2, config):
        for node_name, update in event.items():
            if update.get("error_type"):
                print(f" Node '{node_name}' caught: {update['error_type']} - {update['error_message']}")
            elif node_name == "finalize":
                print(f" Final Result: {update['final_analysis']}")

if __name__ == "__main__":
    asyncio.run(run_compliance_stream())

Enterprise Benefits of State-Driven Error Hierarchies

  1. Granular, Automated Self-Healing: By mapping specific Python exceptions to specific LangGraph recovery nodes, the system heals itself. An API failure triggers a backoff; a timeout triggers a model downgrade. The pipeline doesn't crash; it adapts.

  2. Complete Observability & Auditing: Because errors are written to the ComplianceState, they are persisted in the LangGraph Memory (Checkpointer). If an auditor asks, "Why was this document flagged as HALTED?", you can query the graph state for that thread_id and see the exact error_message and api_retry_count at the time of failure.

  3. Decoupled Business Logic from Error Handling: The core agent nodes (validate, fetch_market_data) focus purely on their primary job. They don't contain complex while loops for retries. The retry logic is cleanly abstracted into dedicated recovery nodes, making the codebase highly maintainable.

  4. SLA Enforcement: By explicitly defining an InferenceTimeoutError and routing to a fallback model, you guarantee that the real-time pipeline meets its latency SLAs, automatically trading a slight dip in model intelligence for a massive gain in system reliability.

Conclusion

In enterprise Multi-Agent systems, exceptions are not just bugs; they are vital signals that dictate system behavior. By implementing a Custom Python Error Hierarchy and integrating it into LangGraph's State and Routing mechanisms, we transform fragile AI scripts into resilient, self-healing enterprise workflows. This architecture ensures that your RAG pipelines can gracefully handle the messy reality of production—bad data, flaky APIs, and slow models without ever dropping the ball or losing the context of what went wrong.

Membership not found