Imitation learning (IL) policies in robotics deliver strong performance in controlled settings but remain brittle in real-world deployments: rare events such as hardware faults, defective parts, unexpected human actions, or any state that lies outside the training distribution can lead to failed executions. Vision-based Anomaly Detection (AD) methods emerged as an appropriate solution to detect these anomalous failure states but do not distinguish failures from benign deviations. We introduce FIDeL (Failure Identification in Demonstration Learning), a policy-independent failure detection module. Leveraging recent AD methods, FIDeL builds a compact representation of nominal demonstrations and aligns incoming observations via optimal transport matching to produce anomaly scores and heatmaps. Spatio-temporal thresholds are derived with an extension of conformal prediction, and a Vision-Language Model (VLM) performs semantic filtering to discriminate benign anomalies from genuine failures. We also introduce BotFails, a multimodal dataset of real-world tasks for failure detection in robotics. FIDeL consistently outperforms state-of-the-art baselines, yielding +5.30% percent AUROC in anomaly detection and +17.38% percent failure-detection accuracy on BotFails compared to existing methods.
Figures & tables
Fig. 1 : We introduce FIDeL , a framework for detecting failures in imitation learning (IL) policies. - Offline - Expert demonstrations are first encoded and stored in a memory buffer M . 0. Conformal Prediction Calibration — A decision threshold is computed from M using Conformal Prediction to determine when a score should be considered anomalous. - Online - 1. Anomaly Detection — During policy execution, anomaly scores and heatmaps are computed from incoming observations. 2. Thresholding — If the score exceeds the calibrated threshold, an anomaly is flagged. 3. Semantic Filtering — Since not all anomalies are failure-related, a VLM filter discards benign deviations and flags only failures that threaten task success.
Fig. 2 : BotFails dataset illustration - all images are illustrations of BotFails tasks executed by the expert - Domestic - 1. clear away the dishes, 2. make coffee, 3. set the table, 4. pour coffee, 5. sort groceries, 6. sort fruits and vegetables - Industrial - 7. sort screws, 8. measure voltage, 9. press buttons, 10. solder.
Fig. 3 : Score illustration - Real- π soldering - episode 15 over 20 episodes of the evaluation set, score obtained with Representation and CP time. The Anomaly Detection score corresponds to the output of the AD module DA(ϕ(YN),ϕt∗) . μpt is obtained when computing DA(ϕ(YN),ϕ(EA)) and allows to compute the Threshold values , see section III-E . When the Anomaly Detection score is below the Threshold , no anomaly is detected ( CP-Normal ) and when it is above, an anomaly is flagged ( CP-Anomalous ). We observe that transitioning from anomaly detection \tiny{1}⃝ to failure detection \tiny{2}⃝ through the use of the VLM reduces the number of false positives (highlighted in the yellow boxes). However, this additional filtering step also introduces a small number of false negatives.
Fig. 4 : Heatmaps illustration - obtained using Representation AD and temporal/spatial CP - Real- π : \tiny{1}⃝ expert, \tiny{2}⃝ benign anomaly: screws present in the work plan, \tiny{3}⃝ failure: dropping the iron - BotFails : \tiny{4}⃝ expert, \tiny{5}⃝ benign anomaly: someone walking in the background (top left corner), \tiny{6}⃝ failure: spilling the cup.
Representation (ours)
logpZ0 [ 12 ]
lopO
AE
STAC [ 11 ]
AUROC ↑
F1@Opt ↑
AUROC ↑
F1@Opt ↑
AUROC ↑
F1@Opt ↑
AUROC ↑
F1@Opt ↑
AUROC ↑
F1@Opt ↑
BotFails
70.50
62.90
65.20
59.87
58.30
53.48
49.90
52.12
N/A
N/A
±0
±0
±0.15
±0.06
±0.70
±0.02
±1.08
±0.08
N/A
N/A
Real- π soldering
86.72
78.29
82.62
78.03
76.16
70.99
81.07
76.33
53.55
63.93
±0
±0
±0.08
±0.02
±0.42
±0.03
±0.88
±0.06
±0
±0
TABLE I : Anomaly Detection evaluation before thresholding – mean AUROC and mean F1-score at optimal threshold ( in % ) for anomaly detection only evaluated on the BotFails dataset and Real- π soldering task , across various AD methods. Best results are highlighted in green and bold. Each task score reflects performance over multiple rollouts (several dozens per task).
Fig. 5 : Anomaly Detection evaluation with thresholding - mean True Positive Rate (TPR), True Negative Rate (TNR), balanced accuracy (Acc), weighted accuracy (W.Acc), ( in % ), for various Anomaly Detection types and various thresholding types–temporal Conformal Prediction (CP time), temporal and spatial Conformal Prediction (CP t&s), Multiple Gaussian–evaluated on real world task from the BotFails dataset and soldering task operated autonomously with ACT [ 3 ] . Best Acc and W.Acc in hatched red.
Fig. 6 : End-to-end system evaluation (including semantic filtering) - accuracy (Acc) and weighted accuracy (W.Acc) for various robotics failure detection systems. The labeling is different for this evaluation. While AD and Threshold module are evaluated using anomaly labels , the end-to-end system is evaluated using failures labels . Which means that all failure-related anomaly labels remain 1, while non-failure anomalies are relabeled from 1 to 0. FiDeL = Representation + CP t&s + Semantic filtering
College of Connected Computing, Vanderbilt University, USA. · School of Computer Science, University of Waterloo, Canada. · School of Computer Science, The University of Sydney, Australia. +1