Agent Cascade Fault & Bottleneck Profiler

Multi-Agent Swarm Failure Simulation & Guardrail Synthesizer

Pipeline DAG & Real-Time Failure Propagation READY • 100 PASSES
Compound Success
60.4%
p95 Latency
6,280 ms
Token Multiplier
3.4x
Amplification
2.3x
Cascade Root Cause Diagnosis
CRITICAL BOTTLENECK action_executor
Unconstrained JSON Schema parameters in Action Executor leading to retry thrashing under schema drift from Knowledge Retriever. Responsible for 63.2% of pipeline failure states.
PRESCRIBED MITIGATIONS
• Insert deterministic Pydantic/Zod validator between Retriever and Executor
• Implement Circuit Breaker after 2 consecutive parameter mismatches
• Cache retriever vector embeddings to prevent duplicate token blowup on retry
Action Executor (Tool Call) EXECUTOR
💡 Modifying node parameters or enabling strict contracts updates pipeline resilience immediately upon simulation.

Deterministic rolls and retry cost

Read the explanation

This page runs one hundred local passes through an authored four-agent fixture. The roll is a repeating arithmetic expression of pass, agent, and attempt indexes, rather than independent random sampling or real model calls. The native default completes all one hundred passes. Moving the selected action executor reliability from seventy eight to fifty percent yields eighty nine successes. At three pixels per successful pass the bars span three hundred and two hundred sixty seven. These are deterministic simulator outcomes. Changing a failure-mode label changes diagnostic text, but the roll itself still compares only effective reliability. An action-executor attempt has a modeled base latency of eighteen hundred fifty milliseconds and costs fourteen hundred tokens. A second attempt multiplies latency by the configured one point five backoff, giving twenty seven hundred seventy five milliseconds. At point one pixels per modeled millisecond the bars span one hundred eighty five and two hundred seventy seven point five. Both attempts together cost twenty eight hundred tokens and forty six hundred twenty five modeled milliseconds. A failed agent halts downstream steps in that pass, so retry cost and downstream cancellation both affect totals. These are accounting rules, not timed provider requests. The written mitigation rule adds twelve percentage points for strict schema, capped at ninety eight, or eight for a circuit-breaker flag, capped at ninety six. Starting from seventy eight gives ninety for schema and eighty six for breaker alone. At three pixels per reliability percentage point the bars span two hundred seventy and two hundred fifty eight. These arbitrary bonuses are not evidence that guardrails achieve those rates. The allowed-attempts expression tests attempts before the loop, when attempts is zero. Therefore enabling the breaker does not actually stop retries at two, despite the older page explanation. Inspect exported node flags and simulation results rather than assuming the label implements a real circuit breaker.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.