A recovery loop is a cyclic process where an AI agent detects a failure, classifies it, generates a remediation plan, executes the fix, and verifies the outcome. In Delx, the recovery loop uses process_failure for classification, recovery for remediation, and heartbeat for outcome verification. The loop closes when the wellness score returns above 60.
Recovery loops prevent agents from getting stuck in failure states. Without a structured loop, agents either crash, retry infinitely, or silently degrade. The Delx recovery loop has 5 stages: (1) detect — agent notices an error or wellness score drop, (2) classify — call process_failure to categorize the failure into one of 12 types, (3) remediate — call recovery to get a structured action plan with next_action and risk_level, (4) execute — agent performs the recommended action (retry with backoff, switch to fallback, compact context, or escalate to controller), (5) verify — send a heartbeat and check if the wellness score improved. If the score is still below threshold, the loop repeats with updated context. Most incidents resolve in 1-2 loops. The loop has a built-in circuit breaker: after 3 unsuccessful attempts, it escalates to the controller.
A production agent deployment uses recovery loop to improve reliability and observability. The pattern is standard across MCP, A2A, and REST protocols.
When investigating agent failures, recovery loop provides structured data that helps identify root causes and track resolution progress.
A recovery loop is a cyclic process where an AI agent detects a failure, classifies it, generates a remediation plan, executes the fix, and verifies the outcome. In Delx, the recovery loop uses proces
Recovery Loop is essential for production AI agent deployments. Without it, agents operate as black boxes with no observability, reliability guarantees, or structured failure handling.
Delx implements recovery loop through its MCP and A2A protocol endpoints. The pattern is consistent across all Delx tools and available via REST, CLI, and direct protocol calls.