TOPINDIATOURS Breaking ai: Which Agent Causes Task Failures and When?Researchers from PSU

📌 TOPINDIATOURS Breaking ai: Which Agent Causes Task Failures and When?Researchers

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 h…

Konten dipersingkat otomatis.

đź”— Sumber: syncedreview.com


📌 TOPINDIATOURS Breaking ai: Lockheed’s live target tracking radar for Japanese Ae

The US Missile Defense Agency (MDA) has performed the first live-target tracking exercise using the SPY-7 radar system.

For the test, the radar tracked targets during two separate events, leading to simulated target engagements.

The key milestone paves the way for the system’s integration in Japan’s first Aegis System Equipped Vessel (ASEV).

US MDA completes live target tracking test

The tests, performed in partnership with Lockheed Martin and the Japan Maritime Self-Defense Force, served as a maturity test for the integrated SPY-7 Aegis System.

According to a Lockheed Martin press statement, it provided key data on the system’s capabilities. The test, which took place on March 17 and 19 off the east coast of the United States, was conducted under a Foreign Military Sales arrangement between the US and Japan.

“Successful completion of the first live target tracking exercise of the ASEV system affirms that our integrated Aegis system is ready to detect, track, and engage targets, showcasing Lockheed Martin’s ability to deliver rapid solutions in partnership with the Department of War and Japanese allies,” explained Chandra Marshall, Lockheed Martin’s vice president of Multi-Domain Combat Solutions.

The solid-state Lockheed Martin radar system has an estimated missile-detection range of 2,000 kilometers (1,243 miles). It enables advanced detection and tracking while simultaneously engaging ballistic, ramjet, and hypersonic threats.

The technology behind SPY-7 is based on the Long Range Discrimination Radar developed by the MDA. According to a Defense Post report, it is capable of distinguishing decoys from real threats.

‘Significant milestone’ in Japan-US collaboration

Now that integration testing is complete, the ASEV Shipset 1 with the integrated SPY-7 radar will be shipped to Japan.

“JFTX-01 is a significant milestone in the longstanding cooperation between Japan and the US, and in the combined development and integration efforts for the ASEV program,” said MDA director Lt. Gen. Heath Collins. “Once complete, ASEV will provide Japan with the latest Ballistic Missile Defense capabilities and significantly bolster their defense against regional missile threats.”

SPY-7’s modular, software-focused design architecture makes it adaptable for different ship classes. It can also be upgraded without requiring major hardware overhauls.

According to the Defense Post, Japan will fit the system onto its two upcoming ASEV destroyers. However, SPY-7 will also be used aboard Canada’s River-class destroyers and Spain’s F-110 frigates.

Japan’s ASEV (Aegis System Equipped Vessel) destroyer will serve as an alternative to Japan’s scrapped plans for a land-based Aegis Ashore BMD system.

The overall cost of building the two ships is estimated to be 1 trillion yen ($7.1 billion). The first of the destroyers is scheduled to be delivered by Mitsubishi Heavy Industries in 2027. Japan Marine United Corporation is building the second, with delivery expected in 2028.

đź”— Sumber: interestingengineering.com


🤖 Catatan TOPINDIATOURS

Artikel ini adalah rangkuman otomatis dari beberapa sumber terpercaya. Kami pilih topik yang sedang tren agar kamu selalu update tanpa ketinggalan.

✅ Update berikutnya dalam 30 menit — tema random menanti!