TRANSMISSION // 2611.13254v1
Failed AI agents often had evidence of their mistakes, a trace study finds
Source published
A preprint examining 95 failed multi-agent runs finds that errors often entered early and persisted despite contradictory evidence. All detailed trajectory annotations were generated by Claude, and the proposed safeguards were not tested as interventions.

An AI agent can notice trouble, change its next action and still preserve the mistaken belief that caused the problem. A new preprint from Villanova University examines that distinction by tracing failures through entire execution logs, rather than assigning a symptom label or identifying a responsible agent and decisive step.
When several language-model agents collaborate, a wrong assumption can travel through plans, messages and verification reports before becoming a wrong answer. Shaohuang Wang and colleagues investigate those paths in a preprint, asking where errors entered, what carried them forward and whether the recorded evidence offered opportunities to intervene.
Their central finding is not simply that agents make mistakes. In many of the failed runs examined, information contradicting the mistake was already available somewhere in the execution history. Detecting trouble also rarely translated into repairing the state that sustained it.
Following the error, not just the symptom
The researchers developed an annotation protocol that distinguishes a candidate fault, the resulting deviation in state and the eventual failure to meet the task specification. Each record connects an origin to subsequent propagation, detection, response and consequence. It also identifies the operational phase and affected state, such as a plan, tool interface or message between agents.
The team produced 96 records from the public Who&When and MAD corpora, covering six multi-agent systems. One run had a correct final answer but a procedural failure, so the main outcome analysis uses 95 failed runs: 88 from Who&When and seven from MAD.
Crucially, the detailed annotations were generated by Claude, with a separate instance reading each complete normalized trajectory. Records passed mechanical checks against the required schema, but that establishes structural consistency, not the correctness of their interpretations. The researchers also compared annotated origins with existing human labels and separately scanned raw logs for a particular harness failure.
Early mistakes, persistent beliefs
Task and knowledge state—including plans, facts and beliefs—was the primary origin domain in 71 of the 95 failures. Wrong decisions made despite adequate information accounted for 40 cases; fabrications accounted for another 25. Fabrication included unsupported claims about results or verification, not just invented prose.
Among the 88 Who&When runs, the median origin position was 18% of the way through the recorded run. The median distance from origin to final symptom was 5.5 steps. In 37 cases, the annotated origin preceded the step that the corpus's human labels identified as decisive. The two labels answer different questions: an early false assumption can precede the later action judged decisive.
Contradictory evidence appeared before the final symptom in 68 of the 95 failed runs. Agents acted on it in only seven. In 41 cases, the evidence entered an agent's input without being mentioned; in 19, an agent acknowledged it but continued unchanged.
A deviation was flagged in 29 runs. Responses, including retries and replanning, appeared in 34, but none fully removed the deviated state; four achieved partial removal. The recurring pattern was a changed next action built on an unchanged mistaken belief.
The surrounding software can fail too
A separate deterministic scan covered all 184 raw Who&When trajectories. It found provider content-filter crashes in 26 of the 58 hand-crafted Magentic-One runs. In 25 of those, the surrounding experiment software—the harness—emitted a final answer that no agent had produced.
Existing corpus labels blamed an agent other than the orchestrator in 21 of those 25 fallback-answer cases. This matters for evaluation: assigning an agent responsibility for an answer generated outside the agent loop can obscure what actually failed. The scan found no corresponding crashes in the 126 algorithm-generated runs.
Suggested safeguards, not demonstrated repairs
The annotations judged independent reviewers using overlooked evidence, fixed task contracts and checks against the environment to be relevant to many episodes. Restoring the agent's own state was judged sufficient in 35 runs; in 56, the faulty plan, brief or stopping rule would instead be replayed.
Those are counterfactual judgments, not measured prevention rates. The researchers did not rerun the systems with these controls installed.
The study also lacks human inter-annotator agreement, uses a non-random partial sample and excludes very long traces. Its small MAD subset is biased toward shorter logs. Because it studies failures rather than representative successes and failures, it cannot estimate how often deployed agents fail. The practical implication is narrower: failure analysis should examine which beliefs survived contradictory evidence, and whether recovery changed those beliefs—not merely whether another attempt occurred.
- LLM agents
- multi-agent systems
- failure analysis
- error propagation
- verification
- agent recovery
- benchmark evaluation
Reviewed cross-references
These connections were reviewed by a model, not independently fact-checked by a human. Similarity does not imply agreement; consult the original papers and the evidence below.
Why an AI agent’s failure needs more than a plausible explanation
Supporting evidence: Wang et al. find that incorrect-verification symptoms span five origin kinds and explicitly distinguish trace-based control-reach judgments from measured interventions; Pakhomov and Nijkamp likewise distinguish transcript attribution from causal evidence and show that restored clones can agree with each other while diverging from live execution. These support the bounded conclusion that diagnostic labels or internal agreement alone do not verify causal failure explanations. The latter replay measurement is model-free, the former study uses LLM annotations of sandbox failures, and neither preprint establishes that its proposed controls improve agent outcomes.
Model review: · openai-codex/gpt-6.1-sol
Evidence and provenance
Selected excerpts, not complete papers. PDF extraction can omit figures or damage equations, tables and reading order; sources may be preprints.
2611.13254v1 — Original paper
Excerpt reference:
static/papers/2611.13254v1.md:781-835
Basis: Paper text
Source SHA-256:447ab3951fa14949eaeaf42f4214658d67dc4a98e3d1e78563c7ad563df5f5f52611.13254v1 — Original paper
Excerpt reference:
static/papers/2611.13254v1.md:836-896
Basis: Paper text
Source SHA-256:447ab3951fa14949eaeaf42f4214658d67dc4a98e3d1e78563c7ad563df5f5f52611.05650v1 — Original paper
Excerpt reference:
static/papers/2611.05650v1.md:78-132
Basis: Paper text
Source SHA-256:1bd2a781c9a903d74be5241a53b2354af2fd58afca587a28bdacd934eee49fae2611.05650v1 — Original paper
Excerpt reference:
static/papers/2611.05650v1.md:233-280
Basis: Paper text
Source SHA-256:1bd2a781c9a903d74be5241a53b2354af2fd58afca587a28bdacd934eee49fae
Related reading
Automatically matched by shared topic keywords. These links do not imply that the sources agree or establish a consensus.
An AI can match a financial answer while using the wrong history
Source published
Shared keywords: benchmark evaluation
EvoML checks machine-learning workflows in stages and saves successful fixes
Source published
Shared keywords: multi agent systems
Why AI Agents Can Agree With Themselves—and Still Fail Each Other
Source published
Shared keywords: llm agents, multi agent systems
An AI coordinator improves answers by directing attempts, not solving problems
Source published
Shared keywords: benchmark evaluation
Coordinated AI agents improve vulnerability exploitation in controlled benchmarks
Source published
Shared keywords: multi agent systems