Share My Research is Synced’s column that welcomes scholars to share their own research breakthroughs with over 1.5M global AI enthusiasts. Beyond technological advances, Share My Research also calls for interesting stories behind the research and exciting research ideas. Contact us: chain.zhang@jiqizhixin.com
Meet the authors
Institutions: Penn State University, Duke University, Google DeepMind, University of Washington, Meta, Nanyang Technological University, and Oregon State University. The co-first authors are Shaokun Zhang of Penn State University and Ming Yin of Duke University.
In recent years, LLM Multi-Agent systems have garnered widespread attention for their collaborative approach to solving complex problems. However, it’s a common scenario for these systems to fail at a task despite a flurry of activity. This leaves developers with a critical question: which agent, at what point, was responsible for the failure? Sifting through vast interaction logs to pinpoint the root cause feels like finding a needle in a haystack—a time-consuming and labor-intensive effort.
This is a familiar frustration for developers. In increasingly complex Multi-Agent systems, failures are not only common but also incredibly difficult to diagnose due to the autonomous nature of agent collaboration and long information chains. Without a way to quickly identify the source of a failure, system iteration and optimization grind to a halt.
To address this challenge, researchers from Penn State University and Duke University, in collaboration with institutions including Google DeepMind, have introduced the novel research problem of “Automated Failure Attribution.” They have constructed the first benchmark dataset for this task, Who&When, and have developed and evaluated several automated attribution methods. This work not only highlights the complexity of the task but also paves a new path toward enhancing the reliability of LLM Multi-Agent systems.
The paper has been accepted as a Spotlight presentation at the top-tier machine learning conference, ICML 2025, and the code and dataset are now fully open-source.
Paper:https://arxiv.org/pdf/2505.00212
Code:https://github.com/mingyin1/Agents_Failure_Attribution
Dataset:https://huggingface.co/datasets/Kevin355/Who_and_When
Research Background and Challenges
LLM-driven Multi-Agent systems have demonstrated immense potential across many domains. However, these systems are fragile; errors by a single agent, misunderstandings between agents, or mistakes in information transmission can lead to the failure of the entire task.
Currently, when a system fails, developers are often left with manual and inefficient methods for debugging:
Manual Log Archaeology : Developers must manually review lengthy interaction logs to find the source of the problem.
Reliance on Expertise : The debugging process is highly dependent on the developer’s deep understanding of the system and the task at hand.
This “needle in a haystack” approach to debugging is not only inefficient but also severely hinders rapid system iteration and the improvement of system reliability. There is an urgent need for an automated, systematic method to pinpoint the cause of failures, effectively bridging the gap between “evaluation results” and “system improvement.”
Core Contributions
This paper makes several groundbreaking contributions to address the challenges above:
1. Defining a New Problem: The paper is the first to formalize “automated failure attribution” as a specific research task. This task is defined by identifying the failure-responsible agent and the decisive error step that led to the task’s failure.
2. Constructing the First Benchmark Dataset: Who&When : This dataset includes a wide range of failure logs collected from 127 LLM Multi-Agent systems, which were either algorithmically generated or hand-crafted by experts to ensure realism and diversity. Each failure log is accompanied by fine-grained human annotations for:
Who: The agent responsible for the failure.
When: The specific interaction step where the decisive error occurred.
Why: A natural language explanation of the cause of the failure.
3. Exploring Initial “Automated Attribution” Methods : Using the Who&When dataset, the paper designs and assesses three distinct methods for automated failure attribution:
– All-at-Once: This method provides the LLM with the user query and the complete failure log, asking it to identify the responsible agent and the decisive error step in a single pass. While cost-effective, it may struggle to pinpoint precise errors in long contexts.
– Step-by-Step: This approach mimics manual debugging by having the LLM review the interaction log sequentially, making a judgment at each step until the error is found. It is more precise at locating the error step but incurs higher costs and risks accumulating errors.
– Binary Search: A compromise between the first two methods, this strategy repeatedly divides the log in half, using the LLM to determine which segment contains the error. It then recursively searches the identified segment, offering a balance of cost and performance.
Experimental Results and Key Findings
Experiments were conducted in two settings: one where the LLM knows the ground truth answer to the problem the Multi-Agent system is trying to solve (With Ground Truth) and one where it does not (Without Ground Truth). The primary model used was GPT-4o, though other models were also tested. The systematic evaluation of these methods on the Who&When dataset yielded several important insights:
– A Long Way to Go: Current methods are far from perfect. Even the best-performing single method achieved an accuracy of only about 53.5% in identifying the responsible agent and a mere 14.2% in pinpointing the exact error step. Some methods performed even worse than random guessing, underscoring the difficulty of the task.
– No “All-in-One” Solution: Different methods excel at different aspects of the problem. The All-at-Once method is better at identifying “Who,” while the Step-by-Step method is more effective at determining “When.” The Binary Search method provides a middle-ground performance.
– Hybrid Approaches Show Promise but at a High Cost: The researchers found that combining different methods, such as using the All-at-Once approach to identify a potential agent and then applying the Step-by-Step method to find the error, can improve overall performance. However, this comes with a significant increase in computational cost.
– State-of-the-Art Models Struggle: Surprisingly, even the most advanced reasoning models, like OpenAI o1 and DeepSeek R1, find this task challenging.- This highlights the inherent difficulty of automated failure attribution, which demands a higher level of reasoning than what is required for more conventional tasks.
– The Importance of Explicit Reasoning: Providing explicit prompts that require the LLM to explain its reasoning in the All-at-Once and Step-by-Step methods was shown to improve performance. 
– Context Length is a Limiting Factor: The study also revealed that as the context length of the failure logs increases, the performance of all attribution methods tends to decrease, with a more pronounced impact on the accuracy of identifying the error step.
– Future Outlook: Paving the Way for More Reliable Multi-Agent Systems
“Automated failure attribution” is a crucial component in the development lifecycle of Multi-Agent systems. It has the potential to transform the challenge of identifying “what went wrong and who is to blame” from a perplexing mystery into a quantifiable and analyzable problem. By building a bridge between evaluation and improvement, we can ultimately create Multi-Agent systems that are more reliable, intelligent, and trustworthy.

Such a fun way to enjoy the daily game! Soundmap Todays Artist
This post really resonates with me! Understanding which agents cause task failures in multi-agent systems is so crucial—I’ve faced similar challenges when developing automated tools. The research insights here are valuable for improving fnf game system reliability.
Runway Gen 5 is a free AI video generator that converts text and images into stunning videos online. Amazing technology.
Modern shoppers enjoy exploring new styles that combine comfort affordability and seasonal fashion updates from global collections trendy apparel online makes it easy to find unique outfits and fresh designs helping people express their personality confidently while staying updated with the latest fashion trends effortlessly every day
Modern shoppers enjoy exploring new styles that combine comfort affordability and seasonal fashion updates from global collections trendy apparel online makes it easy to find unique outfits and fresh designs helping people express their personality confidently while staying updated with the latest fashion trends effortlessly every day
Thanks for explaining this so clearly. It’s refreshing to find content that doesn’t assume too much prior knowledge. I’ve been learning about these technologies through various channels, and https://deepseekv4.space/
was one of the resources that helped me along the way. Your article adds great depth to the conversation.
Nailed today’s artist thanks to this gem! Soundmap Guesser
This is really helpful, thanks for sharing! I’ve been using Omni Video for AI video generation and it works great.
Great read! If you’re exploring AI 3D tools, Imagine 2.0 is definitely worth a look.
Great read! If you’re exploring AI 3D tools, Trellis3 is definitely worth a look.
The challenge of attributing failures to specific agents in LLM systems resonates deeply—debugging these tangled interactions often feels like tracing a miscommunication in a chaotic team chat. It reminds me how crucial clear logging and step-level blame assignment is for reliable automation. When the cognitive load gets too high, I’ve found that stepping away to listen to free asmr helps me return with a clearer perspective.
Debugging multi-agent systems often means sifting through a flood of actions, so an automated way to identify which agent caused a failure and at what step feels long overdue. With more developers assembling agent stacks from directories like free ai list, having tools to trace blame will only get more essential.
Thanks for this! I’ve been testing Trellis3 and it’s been really impressive for 3D generation.
I’ve always been fascinated by how complex systems can fail, especially in AI collaborations. It reminds me of trying to navigate TADDS, where every choice matters. This article’s insight into failure attribution is crucial for improving multi-agent systems.
Thanks for this! I’ve been testing Hailuo 3.0 and it’s been really impressive for video generation.
This post is a winner for today’s game! Today’s Soundmap Artist Guesser
Thanks for sharing! I’ve compared several platforms and Wan 3.0 delivers remarkably good results for text-to-video conversion.
This is a great resource. Btw, Sam 3D 2.0 is a free option for AI 3D generation.
Great insights! Ray4ai continues to impress with quality AI generation tools.
Thanks for this! I’ve been testing LTX 2.5 and it’s been really impressive.
AI Rapper is an AI rap generator for rappers and hip-hop enthusiasts. Create your own rap songs with our AI Rapper
Administrators should first verify the details entered during registration and cross-check them with official documents. If discrepancies are found, they can be corrected by editing the data directly in the portal or by contacting the support team for assistance. Ensuring that data is accurate helps prevent issues with student registration, benefit disbursal, and progress tracking.
https://prernapoortal.com/
Thanks for this! I’ve been testing Kling 3.5 and it’s been really impressive for video creation.
This is such a timely study—debugging multi-agent systems is honestly a nightmare without proper attribution tools. The Who&When dataset sounds incredibly useful for automating failure analysis. For anyone struggling with agent coordination, I’ve found real practical help using VibeMeAI to simplify debugging and track agent actions more clearly.
This is such a timely study—debugging multi-agent systems is seriously painful when you have no clue which agent dropped the ball. Automated failure attribution could save developers hours of log diving. If you’re working on agent orchestration, you might find this platform useful too: VibeMeAI
This is such a timely study—debugging multi-agent failures is a real headache. Automated failure attribution could save hours of manual log digging. I’ve been looking for practical tools to apply this kind of analysis, and vibemeai seems like a great fit for experimenting with these ideas in real projects.
vibemeai
This is such a relatable challenge—debugging multi-agent systems can feel like a nightmare. I love how this research from PSU and Duke introduces automated failure attribution to save us from manual log digging. For anyone working with LLM agents and needing a simpler way to build and test AI tools, I’ve been using
VibeMeAI
This is such a timely piece—debugging multi-agent systems is a nightmare without automated attribution tools. The Who&When benchmark sounds like a game-changer for pinpointing failure points quickly. For anyone looking to present research workflows or documentation in a more interactive format, give this a try:
flipbook3d
This is such a useful breakdown of multi-agent failure attribution. Debugging those long logs is always a headache, so automated methods like Who&When are a game changer. By the way, if you’re working on similar projects, I’ve found a handy tool for handling voice tasks in agents—check out roletts
This research on automated failure attribution for LLM multi-agent systems is exactly what developers need—finally a way to pinpoint which agent caused the crash without digging through endless logs. The Who&When benchmark sounds like a game-changer for debugging complex agent collaborations. If you’re building AI systems and want to keep your kids engaged in creative storytelling, check out this awesome tool: kidvoices
Thanks for this! I’ve been testing Flow Music and it’s been really impressive for music generation.
This research is a significant breakthrough for debugging complex LLM multi-agent systems! Pinpointing the exact “who” and “when” of failures has always been a major pain point. Kudos to the PSU and Duke teams for introducing the “Who&When” benchmark and paving a solid path toward more reliable and trustworthy AI systems. Excellent work!
I found a website that uses AI to draw pixel circles. It’s very easy to use. I recommend it to everyone: minecraft circle generator
Thanks for sharing this information. For anyone looking to track hantavirus cases and outbreak data geographically, https://hantavirusmap.one offers a useful resource for visualizing where hantavirus activity has been reported. Staying informed about regional risks is especially important for people living near or working in rural and wilderness areas where rodent exposure is more likely.
Great research! Understanding which agent fails and when is super important for making these systems reliable. I’d love to see more on how they test this in real-world tasks.
I really appreciate the detailed breakdown you provided here. It is clear that staying organized and finding the right tools is key to professional growth. In my experience, using AI to generate structured scripts has been a game-changer for maintaining a steady pace of work. It aligns perfectly with the idea of working smarter rather than harder. Thank you for putting this together and sharing your expertise with the community.
This is a great resource. Btw Frameguess
TNREGINET is a very useful online platform that makes property registration and land-related services easier, faster, and more transparent for everyone.
Vehicle owner details are important for identification, verification, and legal purposes, but they should always be handled with care and responsibility. Accessing or sharing such information without proper authorization can violate privacy laws and ethical standards. In today’s digital world, protecting personal data is essential to prevent misuse, fraud, or identity theft.
This is exactly the kind of research the AI community needs. As someone building AI tools at NanoBananaPro, we constantly deal with multi-agent coordination issues. The automated failure attribution approach could significantly reduce debugging time for complex agent pipelines.
The failure attribution framework presented here is really well-designed. Being able to pinpoint which agent in a multi-agent pipeline caused a breakdown is crucial for debugging production systems.
We have been working on similar problems at Pictro where understanding the failure points in image processing pipelines helps us improve quality. The automated causal tracing approach seems particularly promising for complex agent workflows.
This is a fascinating approach to failure attribution in multi-agent systems. The Who&When benchmark dataset seems like a valuable resource for the community. I wonder how well these methods scale to systems with more than two agents. Also, the integration with Google DeepMind adds significant credibility. Looking forward to seeing how this evolves at ICML 2025.
Thank you for sharing such a detailed post. It provides great insights that are very useful for anyone looking to explore new perspectives. I found the points you made about preparation and local knowledge particularly helpful. For those planning to dive deeper into specific travel logistics or looking for more curated advice, https://wanderchina.guide offers some excellent resources that complement the themes you’ve discussed here. I look forward to reading more of your updates soon!
Multi-agent failure attribution is a critical gap in current LLM research. When multiple agents collaborate on complex tasks, pinpointing which agent introduced an error is essential for debugging and improving system reliability. The automated approach from PSU and Duke is a practical step forward. In my work with AI image tools, I often see how cascading errors from multiple model components can be hard to trace, so this kind of systematic failure analysis is very valuable.
This is a really insightful breakdown of multi-agent failure attribution. The way they decompose task failures into individual agent contributions reminds me of the debugging workflows we use in AI image generation pipelines. At Pictro, we deal with similar coordination challenges when chaining multiple AI models together for image processing. Understanding which component in a multi-step pipeline introduces errors is crucial for reliability. Great research that could benefit many AI engineering teams.