A failure ladder for retrieval-augmented agents
A wrong answer is the final symptom of failures that may begin with source coverage, access control, parsing, retrieval, context assembly, generation or action.
Fault handling, compensation, rollback and graceful recovery for agent workflows.
A wrong answer is the final symptom of failures that may begin with source coverage, access control, parsing, retrieval, context assembly, generation or action.
A useful tabletop follows one plausible agent failure through detection, containment, evidence, business recovery and accountable return to service.
Maintenance agents can turn condition signals into coordinated work, but plant safety and control demand bounded action and field verification.
Long-running agent work cannot rely on a transcript and hopeful retries. Explicit state makes progress, authority, recovery and completion inspectable across failures.
Multi-agent systems fail between workers when goals, evidence, state, authority and completion semantics do not survive the transfer. Test the protocol, not just each agent.
Retries, duplicated messages and uncertain tool outcomes can multiply an agent’s effects. Idempotency turns a logical action into one controlled business operation.
Long-running agents accumulate state, dependencies and chances to drift. Evaluation must test checkpoints, recovery, changing conditions and complete outcomes across time.
A logistics agent earns trust when data becomes late, routes close and plans conflict—not when everything follows the timetable.
Inject realistic faults, verify state and judge the recovery path. A retry that finishes the task can still duplicate work or hide uncertainty.
KEEP EXPLORING
Read the method, assumptions and questions to ask.